Methods and systems for managing data

ABSTRACT

Computationally implemented methods and systems include identifying one or more services configured to be provided to a user of a device, said identifying at least partly based on data regarding one or more properties of the device, requesting access to data collected by one or more portions of the device, in exchange for providing at least a portion of one of the one or more identified services, and providing at least a portion of the one or more services after receiving access to the data collectable by one or more portions of the device. In addition to the foregoing, other aspects are described in the claims, drawings, and text.

CROSS-REFERENCE TO RELATED APPLICATIONS

If an Application Data Sheet (ADS) has been filed on the filing date ofthis application, it is incorporated by reference herein. Anyapplications claimed on the ADS for priority under 35 U.S.C. §§119, 120,121, or 365(c), and any and all parent, grandparent, great-grandparent,etc. applications of such applications, are also incorporated byreference, including any priority claims made in those applications andany material incorporated by reference, to the extent such subjectmatter is not inconsistent herewith.

The present application is related to and/or claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Priority Applications”), if any, listed below(e.g., claims earliest available priority dates for other thanprovisional patent applications or claims benefits under 35 USC §119(e)for provisional patent applications, for any and all parent,grandparent, great-grandparent, etc. applications of the PriorityApplication(s)). In addition, the present application is related to the“Related Applications,” if any, listed below.

Priority Applications

For purposes of the USPTO extra-statutory requirements, the presentapplication claims benefit of priority of U.S. Provisional PatentApplication No. 61/720,245 titled METHODS AND SYSTEMS FOR DATA SERVICES,naming Edward K. Y. Jung, Royce A. Levien, Richard T. Lord, Robert W.Lord, and Mark A. Malamud as inventors, filed 30 Oct. 2012, which wasfiled within the twelve months preceding the filing date of the presentapplication or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication claims benefit of priority of U.S. Provisional PatentApplication No. 61/720,874 titled METHODS AND SYSTEMS FOR DATA SERVICES,naming Edward K. Y. Jung, Royce A. Levien, Richard T. Lord, Robert W.Lord, and Mark A. Malamud as inventors, filed 31 Oct. 2012, which wasfiled within the twelve months preceding the filing date of the presentapplication or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

Related Applications

U.S. patent application Ser. No. To Be Assigned, entitled METHODS ANDSYSTEMS FOR MANAGING DATA, naming Edward K. Y. Jung, Royce A. Levien,Richard T. Lord, Robert W. Lord, and Mark A. Malamud as inventors, filed26 Nov. 2012 with attorney docket no. 0712-003-013-000000, is related tothe present application.

U.S. patent application Ser. No. To Be Assigned, entitled METHODS ANDSYSTEMS FOR MANAGING DATA, naming Edward K. Y. Jung, Royce A. Levien,Richard T. Lord, Robert W. Lord, and Mark A. Malamud as inventors, filed26 Nov. 2012 with attorney docket no. 0712-003-013-C00001, is related tothe present application.

U.S. patent application Ser. No. To Be Assigned, entitled METHODS ANDSYSTEMS FOR MANAGING DATA, naming Edward K. Y. Jung, Royce A. Levien,Richard T. Lord, Robert W. Lord, and Mark A. Malamud as inventors, filed26 Nov. 2012 with attorney docket no. 0712-003-014-C00001, is related tothe present application.

U.S. patent application Ser. No. To Be Assigned, entitled METHODS ANDSYSTEMS FOR MANAGING DATA, naming Edward K. Y. Jung, Royce A. Levien,Richard T. Lord, Robert W. Lord, and Mark A. Malamud as inventors, filed26 Nov. 2012 with attorney docket no. 0712-003-015-000000, is related tothe present application.

U.S. patent application Ser. No. To Be Assigned, entitled METHODS ANDSYSTEMS FOR MANAGING DATA, naming Edward K. Y. Jung, Royce A. Levien,Richard T. Lord, Robert W. Lord, and Mark A. Malamud as inventors, filed26 Nov. 2012 with attorney docket no. 0712-003-015-C00001, is related tothe present application.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation, continuation-in-part, or divisional of a parentapplication. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTOOfficial Gazette Mar. 18, 2003. The USPTO further has provided forms forthe Application Data Sheet which allow automatic loading ofbibliographic data but which require identification of each applicationas a continuation, continuation-in-part, or divisional of a parentapplication. The present Applicant Entity (hereinafter “Applicant”) hasprovided above a specific reference to the application(s) from whichpriority is being claimed as recited by statute. Applicant understandsthat the statute is unambiguous in its specific reference language anddoes not require either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant has provided designation(s) of arelationship between the present application and its parentapplication(s) as set forth above and in any ADS filed in thisapplication, but expressly points out that such designation(s) are notto be construed in any way as any type of commentary and/or admission asto whether or not the present application contains any new matter inaddition to the matter of its parent application(s).

If the listings of applications provided above are inconsistent with thelistings provided via an ADS, it is the intent of the Applicant to claimpriority to each application that appears in the Priority Applicationssection of the ADS and to each application that appears in the PriorityApplications section of this application.

All subject matter of the Priority Applications and the RelatedApplications and of any and all parent, grandparent, great-grandparent,etc. applications of the Priority Applications and the RelatedApplications, including any priority claims, is incorporated herein byreference to the extent such subject matter is not inconsistentherewith.

BACKGROUND

This application is related to data services.

SUMMARY

In one or more various aspects, a method includes but is not limited toidentifying one or more services configured to be provided to a user ofa device, said identifying at least partly based on data regarding oneor more properties of the device, requesting access to data collected byone or more portions of the device, in exchange for providing at least aportion of one of the one or more identified services, and providing atleast a portion of the one or more services after receiving access tothe data collectable by one or more portions of the device. In additionto the foregoing, other method aspects are described in the claims,drawings, and text forming a part of the disclosure set forth herein.

In one or more various aspects, one or more related systems may beimplemented in machines, compositions of matter, or manufactures ofsystems, limited to patentable subject matter under 35 U.S.C. 101. Theone or more related systems may include, but are not limited to,circuitry and/or programming for effecting the herein referenced methodaspects. The circuitry and/or programming may be virtually anycombination of hardware, software, and/or firmware configured to effectthe herein referenced method aspects depending upon the design choicesof the system designer, and limited to patentable subject matter under35 USC 101.

In one or more various aspects, a system includes, but is not limitedto, means for identifying one or more services configured to be providedto a user of a device, said identifying at least partly based on dataregarding one or more properties of the device, means for requestingaccess to data collected by one or more portions of the device, inexchange for providing at least a portion of one of the one or moreidentified services, and means for providing at least a portion of theone or more services after receiving access to the data collectable byone or more portions of the device. In addition to the foregoing, othersystem aspects are described in the claims, drawings, and text forming apart of the disclosure set forth herein.

In one or more various aspects, a system includes, but is not limitedto, circuitry for identifying one or more services configured to beprovided to a user of a device, said identifying at least partly basedon data regarding one or more properties of the device, circuitry forrequesting access to data collected by one or more portions of thedevice, in exchange for providing at least a portion of one of the oneor more identified services, and circuitry for providing at least aportion of the one or more services after receiving access to the datacollectable by one or more portions of the device. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the disclosure set forth herein.

In one or more various aspects, a computer program product, comprising asignal bearing medium, bearing one or more instructions including, butnot limited to, one or more instructions for identifying one or moreservices configured to be provided to a user of a device, saididentifying at least partly based on data regarding one or moreproperties of the device, one or more instructions for requesting accessto data collected by one or more portions of the device, in exchange forproviding at least a portion of one of the one or more identifiedservices, and one or more instructions for providing at least a portionof the one or more services after receiving access to the datacollectable by one or more portions of the device. In addition to theforegoing, other computer program product aspects are described in theclaims, drawings, and text forming a part of the disclosure set forthherein.

In one or more various aspects, a device is defined by a computationallanguage, such that the device comprises one or more interchainedphysical machines ordered for identifying one or more servicesconfigured to be provided to a user of a device, said identifying atleast partly based on data regarding one or more properties of thedevice, one or more interchained physical machines ordered forrequesting access to data collected by one or more portions of thedevice, in exchange for providing at least a portion of one of the oneor more identified services, and one or more interchained physicalmachines ordered for providing at least a portion of the one or moreservices after receiving access to the data collectable by one or moreportions of the device.

In addition to the foregoing, various other method and/or system and/orprogram product aspects are set forth and described in the teachingssuch as text (e.g., claims and/or detailed description) and/or drawingsof the present disclosure.

The foregoing is a summary and thus may contain simplifications,generalizations, inclusions, and/or omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is NOT intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matter described herein will become apparent by referenceto the detailed description, the corresponding drawings, and/or in theteachings set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

For a more complete understanding of embodiments, reference now is madeto the following descriptions taken in connection with the accompanyingdrawings. The use of the same symbols in different drawings typicallyindicates similar or identical items, unless context dictates otherwise.The illustrative embodiments described in the detailed description,drawings, and claims are not meant to be limiting. Other embodiments maybe utilized, and other changes may be made, without departing from thespirit or scope of the subject matter presented here.

FIG. 1A shows a high-level block diagram of an exemplary environment100, according to an embodiment.

FIG. 1B shows a high-level block diagram of a computing device 130operating in an exemplary environment 100, according to an embodiment.

FIG. 1C shows a high level block diagram of a computing device 130Aoperating in an exemplary embodiment 100′, according to an embodiment.

FIG. 1D shows a high-level block diagram of a computing device 130Boperating in an exemplary embodiment 100″, according to an embodiment.

FIG. 2, including FIGS. 2A-2H, shows a particular perspective of theidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on device datamodule 152 of processing module 150 of computing device 130 of FIG. 1B,according to an embodiment.

FIG. 3, including FIGS. 3A-3D, shows a particular perspective of theaccess to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingmodule 154 of processing module 150 of computing device 130 of FIG. 1B,according to an embodiment.

FIG. 4, including FIGS. 4A-4B, shows a particular perspective of theprovision of at least a portion of the one or more services facilitatingupon receipt of negotiated access to data acquired by the device module156 of processing module 150 of computing device 130 of FIG. 1B,according to an embodiment.

FIG. 5 is a high-level logic flowchart of a process, e.g., operationalflow 500, according to an embodiment.

FIG. 6A is a high-level logic flow chart of a process depictingalternate implementations of an identifying services operation 502,according to one or more embodiments.

FIG. 6B is a high-level logic flow chart of a process depictingalternate implementations of an identifying services operation 502,according to one or more embodiments.

FIG. 6C is a high-level logic flow chart of a process depictingalternate implementations of an identifying services operation 502,according to one or more embodiments.

FIG. 6D is a high-level logic flow chart of a process depictingalternate implementations of an identifying services operation 502,according to one or more embodiments.

FIG. 6E is a high-level logic flow chart of a process depictingalternate implementations of an identifying services operation 502,according to one or more embodiments.

FIG. 6F is a high-level logic flow chart of a process depictingalternate implementations of an identifying services operation 502,according to one or more embodiments.

FIG. 6G is a high-level logic flow chart of a process depictingalternate implementations of an identifying services operation 502,according to one or more embodiments.

FIG. 6H is a high-level logic flow chart of a process depictingalternate implementations of an identifying services operation 502,according to one or more embodiments.

FIG. 6I is a high-level logic flow chart of a process depictingalternate implementations of an identifying services operation 502,according to one or more embodiments.

FIG. 7A is a high-level logic flow chart of a process depictingalternate implementations of a data access requesting operation 504,according to one or more embodiments.

FIG. 7B is a high-level logic flow chart of a process depictingalternate implementations of a data access requesting operation 504,according to one or more embodiments.

FIG. 7C is a high-level logic flow chart of a process depictingalternate implementations of a data access requesting operation 504,according to one or more embodiments.

FIG. 7D is a high-level logic flow chart of a process depictingalternate implementations of a data access requesting operation 504,according to one or more embodiments.

FIG. 7E is a high-level logic flow chart of a process depictingalternate implementations of a data access requesting operation 504,according to one or more embodiments.

FIG. 8A is a high-level logic flow chart of a process depictingalternate implementations of a providing operation 506, according to oneor more embodiments.

FIG. 8B is a high-level logic flow chart of a process depictingalternate implementations of a providing operation 506, according to oneor more embodiments.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar or identical components oritems, unless context dictates otherwise. The illustrative embodimentsdescribed in the detailed description, drawings, and claims are notmeant to be limiting. Other embodiments may be utilized, and otherchanges may be made, without departing from the spirit or scope of thesubject matter presented here.

Thus, in accordance with various embodiments, computationallyimplemented methods, systems, circuitry, articles of manufacture,ordered chains of matter, and computer program products are designed to,among other things, provide an interface for identifying one or moreservices configured to be provided to a user of a device, saididentifying at least partly based on data regarding one or moreproperties of the device, requesting access to data collected by one ormore portions of the device, in exchange for providing at least aportion of one of the one or more identified services, and providing atleast a portion of the one or more services after receiving access tothe data collectable by one or more portions of the device.

The claims, description, and drawings of this application may describeone or more of the instant technologies in operational/functionallanguage, for example as a set of operations to be performed by acomputer. Such operational/functional description in most instanceswould be understood by one skilled the art as specifically-configuredhardware (e.g., because a general purpose computer in effect becomes aspecial purpose computer once it is programmed to perform particularfunctions pursuant to instructions from program software).

Importantly, although the operational/functional descriptions describedherein are understandable by the human mind, they are not abstract ideasof the operations/functions divorced from computational implementationof those operations/functions. Rather, the operations/functionsrepresent a specification for the massively complex computationalmachines or other means. As discussed in detail below, theoperational/functional language must be read in its proper technologicalcontext, i.e., as concrete specifications for physical implementations.

The logical operations/functions described herein are a distillation ofmachine specifications or other physical mechanisms specified by theoperations/functions such that the otherwise inscrutable machinespecifications may be comprehensible to the human mind. The distillationalso allows one of skill in the art to adapt the operational/functionaldescription of the technology across many different specific vendors'hardware configurations or platforms, without being limited to specificvendors' hardware configurations or platforms.

Some of the present technical description (e.g., detailed description,drawings, claims, etc.) may be set forth in terms of logicaloperations/functions. As described in more detail in the followingparagraphs, these logical operations/functions are not representationsof abstract ideas, but rather representative of static or sequencedspecifications of various hardware elements. Differently stated, unlesscontext dictates otherwise, the logical operations/functions will beunderstood by those of skill in the art to be representative of staticor sequenced specifications of various hardware elements. This is truebecause tools available to one of skill in the art to implementtechnical disclosures set forth in operational/functional formats—toolsin the form of a high-level programming language (e.g., C, java, visualbasic), etc.), or tools in the form of Very high speed HardwareDescription Language (“VHDL,” which is a language that uses text todescribe logic circuits)—are generators of static or sequencedspecifications of various hardware configurations. This fact issometimes obscured by the broad term “software,” but, as shown by thefollowing explanation, those skilled in the art understand that what istermed “software” is a shorthand for a massively complexinterchaining/specification of ordered-matter elements. The term“ordered-matter elements” may refer to physical components ofcomputation, such as assemblies of electronic logic gates, molecularcomputing logic constituents, quantum computing mechanisms, etc.

For example, a high-level programming language is a programming languagewith strong abstraction, e.g., multiple levels of abstraction, from thedetails of the sequential organizations, states, inputs, outputs, etc.,of the machines that a high-level programming language actuallyspecifies. See, e.g., Wikipedia, High-level programming language,http://en.wikipedia.org/wiki/High-levelprogramming_language (as of Jun.5, 2012, 21:00 GMT). In order to facilitate human comprehension, in manyinstances, high-level programming languages resemble or even sharesymbols with natural languages. See, e.g., Wikipedia, Natural language,http://en.wikipedia.org/wiki/Natural_language (as of Jun. 5, 2012, 21:00GMT).

It has been argued that because high-level programming languages usestrong abstraction (e.g., that they may resemble or share symbols withnatural languages), they are therefore a “purely mental construct.”(e.g., that “software”—a computer program or computer programming—issomehow an ineffable mental construct, because at a high level ofabstraction, it can be conceived and understood in the human mind). Thisargument has been used to characterize technical description in the formof functions/operations as somehow “abstract ideas.” In fact, intechnological arts (e.g., the information and communicationtechnologies) this is not true.

The fact that high-level programming languages use strong abstraction tofacilitate human understanding should not be taken as an indication thatwhat is expressed is an abstract idea. In fact, those skilled in the artunderstand that just the opposite is true. If a high-level programminglanguage is the tool used to implement a technical disclosure in theform of functions/operations, those skilled in the art will recognizethat, far from being abstract, imprecise, “fuzzy,” or “mental” in anysignificant semantic sense, such a tool is instead a nearincomprehensibly precise sequential specification of specificcomputational machines—the parts of which are built up byactivating/selecting such parts from typically more generalcomputational machines over time (e.g., clocked time). This fact issometimes obscured by the superficial similarities between high-levelprogramming languages and natural languages. These superficialsimilarities also may cause a glossing over of the fact that high-levelprogramming language implementations ultimately perform valuable work bycreating/controlling many different computational machines.

The many different computational machines that a high-level programminglanguage specifies are almost unimaginably complex. At base, thehardware used in the computational machines typically consists of sometype of ordered matter (e.g., traditional electronic devices (e.g.,transistors), deoxyribonucleic acid (DNA), quantum devices, mechanicalswitches, optics, fluidics, pneumatics, optical devices (e.g., opticalinterference devices), molecules, etc.) that are arranged to form logicgates. Logic gates are typically physical devices that may beelectrically, mechanically, chemically, or otherwise driven to changephysical state in order to create a physical reality of Boolean logic.

Logic gates may be arranged to form logic circuits, which are typicallyphysical devices that may be electrically, mechanically, chemically, orotherwise driven to create a physical reality of certain logicalfunctions. Types of logic circuits include such devices as multiplexers,registers, arithmetic logic units (ALUs), computer memory, etc., eachtype of which may be combined to form yet other types of physicaldevices, such as a central processing unit (CPU)—the best known of whichis the microprocessor. A modern microprocessor will often contain morethan one hundred million logic gates in its many logic circuits (andoften more than a billion transistors). See, e.g., Wikipedia, Logicgates, http://en.wikipedia.org/wiki/Logic_gates (as of Jun. 5, 2012,21:03 GMT).

The logic circuits forming the microprocessor are arranged to provide amicroarchitecture that will carry out the instructions defined by thatmicroprocessor's defined Instruction Set Architecture. The InstructionSet Architecture is the part of the microprocessor architecture relatedto programming, including the native data types, instructions,registers, addressing modes, memory architecture, interrupt andexception handling, and external Input/Output. See, e.g., Wikipedia,Computer architecture,http://en.wikipedia.org/wiki/Computer_architecture (as of Jun. 5, 2012,21:03 GMT).

The Instruction Set Architecture includes a specification of the machinelanguage that can be used by programmers to use/control themicroprocessor. Since the machine language instructions are such thatthey may be executed directly by the microprocessor, typically theyconsist of strings of binary digits, or bits. For example, a typicalmachine language instruction might be many bits long (e.g., 32, 64, or128 bit strings are currently common). A typical machine languageinstruction might take the form “11110000101011110000111100111111” (a 32bit instruction).

It is significant here that, although the machine language instructionsare written as sequences of binary digits, in actuality those binarydigits specify physical reality. For example, if certain semiconductorsare used to make the operations of Boolean logic a physical reality, theapparently mathematical bits “1” and “0” in a machine languageinstruction actually constitute a shorthand that specifies theapplication of specific voltages to specific wires. For example, in somesemiconductor technologies, the binary number “1” (e.g., logical “1”) ina machine language instruction specifies around +5 volts applied to aspecific “wire” (e.g., metallic traces on a printed circuit board) andthe binary number “0” (e.g., logical “0”) in a machine languageinstruction specifies around −5 volts applied to a specific “wire.” Inaddition to specifying voltages of the machines' configuration, suchmachine language instructions also select out and activate specificgroupings of logic gates from the millions of logic gates of the moregeneral machine. Thus, far from abstract mathematical expressions,machine language instruction programs, even though written as a stringof zeros and ones, specify many, many constructed physical machines orphysical machine states.

Machine language is typically incomprehensible by most humans (e.g., theabove example was just ONE instruction, and some personal computersexecute more than two billion instructions every second). See, e.g.,Wikipedia, Instructions per second,http://en.wikipedia.org/wiki/Instructions_per_second (as of Jun. 5,2012, 21:04 GMT). Thus, programs written in machine language—which maybe tens of millions of machine language instructions long—areincomprehensible. In view of this, early assembly languages weredeveloped that used mnemonic codes to refer to machine languageinstructions, rather than using the machine language instructions'numeric values directly (e.g., for performing a multiplicationoperation, programmers coded the abbreviation “mult,” which representsthe binary number “011000” in MIPS machine code). While assemblylanguages were initially a great aid to humans controlling themicroprocessors to perform work, in time the complexity of the work thatneeded to be done by the humans outstripped the ability of humans tocontrol the microprocessors using merely assembly languages.

At this point, it was noted that the same tasks needed to be done overand over, and the machine language necessary to do those repetitivetasks was the same. In view of this, compilers were created. A compileris a device that takes a statement that is more comprehensible to ahuman than either machine or assembly language, such as “add 2+2 andoutput the result,” and translates that human understandable statementinto a complicated, tedious, and immense machine language code (e.g.,millions of 32, 64, or 128 bit length strings). Compilers thus translatehigh-level programming language into machine language.

This compiled machine language, as described above, is then used as thetechnical specification which sequentially constructs and causes theinteroperation of many different computational machines such thathumanly useful, tangible, and concrete work is done. For example, asindicated above, such machine language—the compiled version of thehigher-level language—functions as a technical specification whichselects out hardware logic gates, specifies voltage levels, voltagetransition timings, etc., such that the humanly useful work isaccomplished by the hardware.

Thus, a functional/operational technical description, when viewed by oneof skill in the art, is far from an abstract idea. Rather, such afunctional/operational technical description, when understood throughthe tools available in the art such as those just described, is insteadunderstood to be a humanly understandable representation of a hardwarespecification, the complexity and specificity of which far exceeds thecomprehension of most any one human. With this in mind, those skilled inthe art will understand that any such operational/functional technicaldescriptions—in view of the disclosures herein and the knowledge ofthose skilled in the art—may be understood as operations made intophysical reality by (a) one or more interchained physical machines, (b)interchained logic gates configured to create one or more physicalmachine(s) representative of sequential/combinatorial logic(s), (c)interchained ordered matter making up logic gates (e.g., interchainedelectronic devices (e.g., transistors), DNA, quantum devices, mechanicalswitches, optics, fluidics, pneumatics, molecules, etc.) that createphysical reality representative of logic(s), or (d) virtually anycombination of the foregoing. Indeed, any physical object which has astable, measurable, and changeable state may be used to construct amachine based on the above technical description. Charles Babbage, forexample, constructed the first computer out of wood and powered bycranking a handle.

Thus, far from being understood as an abstract idea, those skilled inthe art will recognize a functional/operational technical description asa humanly-understandable representation of one or more almostunimaginably complex and time sequenced hardware instantiations. Thefact that functional/operational technical descriptions might lendthemselves readily to high-level computing languages (or high-levelblock diagrams for that matter) that share some words, structures,phrases, etc. with natural language simply cannot be taken as anindication that such functional/operational technical descriptions areabstract ideas, or mere expressions of abstract ideas. In fact, asoutlined herein, in the technological arts this is simply not true. Whenviewed through the tools available to those of skill in the art, suchfunctional/operational technical descriptions are seen as specifyinghardware configurations of almost unimaginable complexity.

As outlined above, the reason for the use of functional/operationaltechnical descriptions is at least twofold. First, the use offunctional/operational technical descriptions allows near-infinitelycomplex machines and machine operations arising from interchainedhardware elements to be described in a manner that the human mind canprocess (e.g., by mimicking natural language and logical narrativeflow). Second, the use of functional/operational technical descriptionsassists the person of skill in the art in understanding the describedsubject matter by providing a description that is more or lessindependent of any specific vendor's piece(s) of hardware.

The use of functional/operational technical descriptions assists theperson of skill in the art in understanding the described subject mattersince, as is evident from the above discussion, one could easily,although not quickly, transcribe the technical descriptions set forth inthis document as trillions of ones and zeroes, billions of single linesof assembly-level machine code, millions of logic gates, thousands ofgate arrays, or any number of intermediate levels of abstractions.However, if any such low-level technical descriptions were to replacethe present technical description, a person of skill in the art couldencounter undue difficulty in implementing the disclosure, because sucha low-level technical description would likely add complexity without acorresponding benefit (e.g., by describing the subject matter utilizingthe conventions of one or more vendor-specific pieces of hardware).Thus, the use of functional/operational technical descriptions assiststhose of skill in the art by separating the technical descriptions fromthe conventions of any vendor-specific piece of hardware.

In view of the foregoing, the logical operations/functions set forth inthe present technical description are representative of static orsequenced specifications of various ordered-matter elements, in orderthat such specifications may be comprehensible to the human mind andadaptable to create many various hardware configurations. The logicaloperations/functions disclosed herein should be treated as such, andshould not be disparagingly characterized as abstract ideas merelybecause the specifications they represent are presented in a manner thatone of skill in the art can readily understand and apply in a mannerindependent of a specific vendor's hardware implementation.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware, software, and/or firmware implementations of aspectsof systems; the use of hardware, software, and/or firmware is generally(but not always, in that in certain contexts the choice between hardwareand software can become significant) a design choice representing costvs. efficiency tradeoffs. Those having skill in the art will appreciatethat there are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software, and/or firmware), and that the preferred vehicle will varywith the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly softwareimplementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software, and/or firmware in one or moremachines, compositions of matter, and articles of manufacture, limitedto patentable subject matter under 35 USC 101. Hence, there are severalpossible vehicles by which the processes and/or devices and/or othertechnologies described herein may be effected, none of which isinherently superior to the other in that any vehicle to be utilized is achoice dependent upon the context in which the vehicle will be deployedand the specific concerns (e.g., speed, flexibility, or predictability)of the implementer, any of which may vary. Those skilled in the art willrecognize that optical aspects of implementations will typically employoptically-oriented hardware, software, and or firmware.

In some implementations described herein, logic and similarimplementations may include software or other control structures.Electronic circuitry, for example, may have one or more paths ofelectrical current constructed and arranged to implement variousfunctions as described herein. In some implementations, one or moremedia may be configured to bear a device-detectable implementation whensuch media hold or transmit device detectable instructions operable toperform as described herein. In some variants, for example,implementations may include an update or modification of existingsoftware or firmware, or of gate arrays or programmable hardware, suchas by performing a reception of or a transmission of one or moreinstructions in relation to one or more operations described herein.Alternatively or additionally, in some variants, an implementation mayinclude special-purpose hardware, software, firmware components, and/orgeneral-purpose components executing or otherwise invokingspecial-purpose components. Specifications or other implementations maybe transmitted by one or more instances of tangible transmission mediaas described herein, optionally by packet transmission or otherwise bypassing through distributed media at various times.

Alternatively or additionally, implementations may include executing aspecial-purpose instruction sequence or invoking circuitry for enabling,triggering, coordinating, requesting, or otherwise causing one or moreoccurrences of virtually any functional operations described herein. Insome variants, operational or other logical descriptions herein may beexpressed as source code and compiled or otherwise invoked as anexecutable instruction sequence. In some contexts, for example,implementations may be provided, in whole or in part, by source code,such as C++, or other code sequences. In other implementations, sourceor other code implementation, using commercially available and/ortechniques in the art, may be compiled//implemented/translated/convertedinto a high-level descriptor language (e.g., initially implementingdescribed technologies in C or C++ programming language and thereafterconverting the programming language implementation into alogic-synthesizable language implementation, a hardware descriptionlanguage implementation, a hardware design simulation implementation,and/or other such similar mode(s) of expression). For example, some orall of a logical expression (e.g., computer programming languageimplementation) may be manifested as a Verilog-type hardware description(e.g., via Hardware Description Language (HDL) and/or Very High SpeedIntegrated Circuit Hardware Descriptor Language (VHDL)) or othercircuitry model which may then be used to create a physicalimplementation having hardware (e.g., an Application Specific IntegratedCircuit). Those skilled in the art will recognize how to obtain,configure, and optimize suitable transmission or computational elements,material supplies, actuators, or other structures in light of theseteachings.

Those skilled in the art will recognize that it is common within the artto implement devices and/or processes and/or systems, and thereafter useengineering and/or other practices to integrate such implemented devicesand/or processes and/or systems into more comprehensive devices and/orprocesses and/or systems. That is, at least a portion of the devicesand/or processes and/or systems described herein can be integrated intoother devices and/or processes and/or systems via a reasonable amount ofexperimentation. Those having skill in the art will recognize thatexamples of such other devices and/or processes and/or systems mightinclude—as appropriate to context and application—all or part of devicesand/or processes and/or systems of (a) an air conveyance (e.g., anairplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., acar, truck, locomotive, tank, armored personnel carrier, etc.), (c) abuilding (e.g., a home, warehouse, office, etc.), (d) an appliance(e.g., a refrigerator, a washing machine, a dryer, etc.), (e) acommunications system (e.g., a networked system, a telephone system, aVoice over IP system, etc.), (f) a business entity (e.g., an InternetService Provider (ISP) entity such as Comcast Cable, Qwest, SouthwesternBell, etc.), or (g) a wired/wireless services entity (e.g., Sprint,Cingular, Nextel, etc.), etc.

In certain cases, use of a system or method may occur in a territoryeven if components are located outside the territory. For example, in adistributed computing context, use of a distributed computing system mayoccur in a territory even though parts of the system may be locatedoutside of the territory (e.g., relay, server, processor, signal-bearingmedium, transmitting computer, receiving computer, etc. located outsidethe territory).

A sale of a system or method may likewise occur in a territory even ifcomponents of the system or method are located and/or used outside theterritory. Further, implementation of at least part of a system forperforming a method in one territory does not preclude use of the systemin another territory

In a general sense, those skilled in the art will recognize that thevarious embodiments described herein can be implemented, individuallyand/or collectively, by various types of electro-mechanical systemshaving a wide range of electrical components such as hardware, software,firmware, and/or virtually any combination thereof, limited topatentable subject matter under 35 U.S.C. 101; and a wide range ofcomponents that may impart mechanical force or motion such as rigidbodies, spring or torsional bodies, hydraulics, electro-magneticallyactuated devices, and/or virtually any combination thereof.Consequently, as used herein “electro-mechanical system” includes, butis not limited to, electrical circuitry operably coupled with atransducer (e.g., an actuator, a motor, a piezoelectric crystal, a MicroElectro Mechanical System (MEMS), etc.), electrical circuitry having atleast one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of memory(e.g., random access, flash, read only, etc.)), electrical circuitryforming a communications device (e.g., a modem, communications switch,optical-electrical equipment, etc.), and/or any non-electrical analogthereto, such as optical or other analogs (e.g., graphene basedcircuitry). Those skilled in the art will also appreciate that examplesof electro-mechanical systems include but are not limited to a varietyof consumer electronics systems, medical devices, as well as othersystems such as motorized transport systems, factory automation systems,security systems, and/or communication/computing systems. Those skilledin the art will recognize that electro-mechanical as used herein is notnecessarily limited to a system that has both electrical and mechanicalactuation except as context may dictate otherwise.

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware,and/or any combination thereof can be viewed as being composed ofvarious types of “electrical circuitry.” Consequently, as used herein“electrical circuitry” includes, but is not limited to, electricalcircuitry having at least one discrete electrical circuit, electricalcircuitry having at least one integrated circuit, electrical circuitryhaving at least one application specific integrated circuit, electricalcircuitry forming a general purpose computing device configured by acomputer program (e.g., a general purpose computer configured by acomputer program which at least partially carries out processes and/ordevices described herein, or a microprocessor configured by a computerprogram which at least partially carries out processes and/or devicesdescribed herein), electrical circuitry forming a memory device (e.g.,forms of memory (e.g., random access, flash, read only, etc.)), and/orelectrical circuitry forming a communications device (e.g., a modem,communications switch, optical-electrical equipment, etc.). Those havingskill in the art will recognize that the subject matter described hereinmay be implemented in an analog or digital fashion or some combinationthereof.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into animage processing system. Those having skill in the art will recognizethat a typical image processing system generally includes one or more ofa system unit housing, a video display device, memory such as volatileor non-volatile memory, processors such as microprocessors or digitalsignal processors, computational entities such as operating systems,drivers, applications programs, one or more interaction devices (e.g., atouch pad, a touch screen, an antenna, etc.), control systems includingfeedback loops and control motors (e.g., feedback for sensing lensposition and/or velocity; control motors for moving/distorting lenses togive desired focuses). An image processing system may be implementedutilizing suitable commercially available components, such as thosetypically found in digital still systems and/or digital motion systems.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into a dataprocessing system. Those having skill in the art will recognize that adata processing system generally includes one or more of a system unithousing, a video display device, memory such as volatile or non-volatilememory, processors such as microprocessors or digital signal processors,computational entities such as operating systems, drivers, graphicaluser interfaces, and applications programs, one or more interactiondevices (e.g., a touch pad, a touch screen, an antenna, etc.), and/orcontrol systems including feedback loops and control motors (e.g.,feedback for sensing position and/or velocity; control motors for movingand/or adjusting components and/or quantities). A data processing systemmay be implemented utilizing suitable commercially available components,such as those typically found in data computing/communication and/ornetwork computing/communication systems.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into a motesystem. Those having skill in the art will recognize that a typical motesystem generally includes one or more memories such as volatile ornon-volatile memories, processors such as microprocessors or digitalsignal processors, computational entities such as operating systems,user interfaces, drivers, sensors, actuators, applications programs, oneor more interaction devices (e.g., an antenna USB ports, acoustic ports,etc.), control systems including feedback loops and control motors(e.g., feedback for sensing or estimating position and/or velocity;control motors for moving and/or adjusting components and/orquantities). A mote system may be implemented utilizing suitablecomponents, such as those found in mote computing/communication systems.Specific examples of such components entail such as Intel Corporation'sand/or Crossbow Corporation's mote components and supporting hardware,software, and/or firmware.

For the purposes of this application, “cloud” computing may beunderstood as described in the cloud computing literature. For example,cloud computing may be methods and/or systems for the delivery ofcomputational capacity and/or storage capacity as a service. The “cloud”may refer to one or more hardware and/or software components thatdeliver or assist in the delivery of computational and/or storagecapacity, including, but not limited to, one or more of a client, anapplication, a platform, an infrastructure, and/or a server The cloudmay refer to any of the hardware and/or software associated with aclient, an application, a platform, an infrastructure, and/or a server.For example, cloud and cloud computing may refer to one or more of acomputer, a processor, a storage medium, a router, a switch, a modem, avirtual machine (e.g., a virtual server), a data center, an operatingsystem, a middleware, a firmware, a hardware back-end, a softwareback-end, and/or a software application. A cloud may refer to a privatecloud, a public cloud, a hybrid cloud, and/or a community cloud. A cloudmay be a shared pool of configurable computing resources, which may bepublic, private, semi-private, distributable, scaleable, flexible,temporary, virtual, and/or physical. A cloud or cloud service may bedelivered over one or more types of network, e.g., a mobilecommunication network, and the Internet.

As used in this application, a cloud or a cloud service may include oneor more of infrastructure-as-a-service (“IaaS”), platform-as-a-service(“PaaS”), software-as-a-service (“SaaS”), and/or desktop-as-a-service(“DaaS”). As a non-exclusive example, IaaS may include, e.g., one ormore virtual server instantiations that may start, stop, access, and/orconfigure virtual servers and/or storage centers (e.g., providing one ormore processors, storage space, and/or network resources on-demand,e.g., EMC and Rackspace). PaaS may include, e.g., one or more softwareand/or development tools hosted on an infrastructure (e.g., a computingplatform and/or a solution stack from which the client can createsoftware interfaces and applications, e.g., Microsoft Azure). SaaS mayinclude, e.g., software hosted by a service provider and accessible overa network (e.g., the software for the application and/or the dataassociated with that software application may be kept on the network,e.g., Google Apps, SalesForce). DaaS may include, e.g., providingdesktop, applications, data, and/or services for the user over a network(e.g., providing a multi-application framework, the applications in theframework, the data associated with the applications, and/or servicesrelated to the applications and/or the data over the network, e.g.,Citrix). The foregoing is intended to be exemplary of the types ofsystems and/or methods referred to in this application as “cloud” or“cloud computing” and should not be considered complete or exhaustive.

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents, and/or wirelessly interactable, and/or wirelesslyinteracting components, and/or logically interacting, and/or logicallyinteractable components.

To the extent that formal outline headings are present in thisapplication, it is to be understood that the outline headings are forpresentation purposes, and that different types of subject matter may bediscussed throughout the application (e.g., device(s)/structure(s) maybe described under process(es)/operations heading(s) and/orprocess(es)/operations may be discussed under structure(s)/process(es)headings; and/or descriptions of single topics may span two or moretopic headings). Hence, any use of formal outline headings in thisapplication is for presentation purposes, and is not intended to be inany way limiting.

Throughout this application, examples and lists are given, withparentheses, the abbreviation “e.g.,” or both. Unless explicitlyotherwise stated, these examples and lists are merely exemplary and arenon-exhaustive. In most cases, it would be prohibitive to list everyexample and every combination. Thus, smaller, illustrative lists andexamples are used, with focus on imparting understanding of the claimterms rather than limiting the scope of such terms.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations are not expressly set forth herein for sakeof clarity.

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

Although user 105 is shown/described herein, e.g., in FIG. 1, and otherplaces, as a single illustrated figure, those skilled in the art willappreciate that user 105 may be representative of one or more humanusers, robotic users (e.g., computational entity), and/or substantiallyany combination thereof (e.g., a user may be assisted by one or morerobotic agents) unless context dictates otherwise. Those skilled in theart will appreciate that, in general, the same may be said of “sender”and/or other entity-oriented terms as such terms are used herein unlesscontext dictates otherwise.

In some instances, one or more components may be referred to herein as“configured to,” “configured by,” “configurable to,” “operable/operativeto,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc.Those skilled in the art will recognize that such terms (e.g.“configured to”) generally encompass active-state components and/orinactive-state components and/or standby-state components, unlesscontext requires otherwise.

In known systems, devices that are associated with one or more users,e.g., phones, tablets, laptops, desktops, cars, game systems,appliances, and the like, may collect data regarding the user. This datamay be desired by third parties. The following describes, among otherimplementations, methods and systems of managing user data collected byone or more devices that may also be useful to entities that are not theuser, and which entities may not necessarily have access to the data.

Referring now to FIG. 1, FIG. 1 illustrates an example environment 100in which the methods, systems, circuitry, articles of manufacture, andcomputer program products and architecture, in accordance with variousembodiments, may be implemented by one or more computing devices 30 Asshown in FIG. 1A, one or more personal devices 20, one or more serviceproviders 70, one or more service developers 60, and one or morecomputing devices 30 may communicate via one or more communicationnetworks 40. In an embodiment, service provider 70 may have one or moreservices that personal device 20 may want. In an embodiment, computingdevice 30, which may be a remote or local server, or distributed set ofservers, may manage data that is gathered, stored, controlled, accessed,restricted, monitored, under the control of, checked, examined,verified, authenticated, authorized, manipulated, updated, altered,filtered, or otherwise acted upon, whether passively or actively, bypersonal device 20. In an embodiment, as described in more detailherein, computing device 30 may have access to some or all of the dataon personal device 20. In another embodiment, computing device 30 mayhave access to only a portion of the data on personal device 20. Instill another embodiment, computing device 30 may have access to amodified version of the data on personal device 20. Specifically, in anembodiment, computing device 20 may have access to the data stored onpersonal device 20, but in anonymous form.

In an embodiment, computing device 30 may offer one or more services topersonal device 20. In an embodiment, the offer of one or more servicesmay be conditional on a grant of access to part or all of the datastored and/or collected by personal device 20. In an embodiment,computing device 30 may receive one or more services from serviceprovider 70 and/or service developer 60, and may select one or more ofthe received services for presentation to the personal device 20. In anembodiment, the data from personal device 20 may be shared with one ormore of service provider 70 and service developer 60. In an embodiment,the data from personal device 20 may be anonymized prior to sharing withservice developer 60 and/or service developer 70.

Referring again to FIG. 1A, FIG. 1A shows a personal device 120.Personal device 120 may be any electronic device, portable or not, thatmay be operated by or associated with one or more users. Personal device120 is shown as interacting with a user 105. As set forth above, user105 may be a person, or a group of people, or another entity that mimicsthe operations of a user. In some embodiments, user 105 may be acomputer or a computer-controlled device. Personal device 120 may be,but is not limited to, a cellular phone, a network phone, a smartphone,a tablet, a music player, a walkie-talkie, a radio, a USB drive, aportable solid state drive, a portable disc-type hard drive, anaugmented reality device (e.g., augmented reality glasses and/orheadphones), earphones, headphones, audio/visual equipment, mediaplayer, television, projection screen, flat screen, monitor, clock,appliance (e.g., microwave, convection oven, stove, refrigerator,freezer), a navigation system (e.g., a Global Positioning System (“GPS”)system), a medical alert device, a remote control, a peripheral, anelectronic safe, an electronic lock, an electronic security system, avideo camera, a personal video recorder, a personal audio recorder, andthe like.

Referring again to FIG. 1A, personal device 120 may include an operatingsystem 124. In this context, operating system 124 refers to anyhardware, software, firmware, and combination thereof which isconsidered at the core or baseline of a device. For example,applications that interact directly with hardware may be considered tobe part of an operating system. In some embodiments, operating system124 may be an FPGA, printed circuit board, or other wired device. In anembodiment, operating system 124 may include one or more of Google'sAndroid, Apple's iOS, Microsoft's Windows, various implementations ofLinux, and the like. In some embodiments, operating system 124 mayinclude a root menu for one or more televisions, stereo systems, mediaplayers, and the like. In some embodiments, operating system 124 may bea “home” screen of a device.

Referring again to FIG. 1A, in an embodiment, personal device 20 mayinclude a user interface 122. User interface 122 may include anyhardware, software, firmware, and combination thereof that allow a user105 to interact with a personal device 120, and for a personal device120 to interact with a user 105. In some embodiments, user interface 122may include a monitor, screen, touchscreen, liquid crystal display(“LCD”) screen, light emitting diode (“LED”) screen, speaker, handset,earpiece, keyboard, keypad, touchpad, mouse, trackball, remote control,button set, microphone, video camera, still camera, a charge-coupleddevice (“CCD”) element, a photovoltaic element, and the like.

Referring again to FIG. 1A, in some embodiments, personal device 120 mayinclude a device memory 126. In some embodiments, device memory 126 mayinclude memory, random access memory (“RAM”), read only memory (“ROM”),flash memory, hard drives, disk-based media, disc-based media, magneticstorage, optical storage, volatile memory, nonvolatile memory, and anycombination thereof. In some embodiments, device memory 126 may beseparated from the device, e.g., available on a different device on anetwork, or over the air. For example, in a networked system, there maybe many personal devices 120 whose device memory 126 is located at acentral server that may be a few feet away or located across an ocean.

Referring again to FIG. 1A, in some embodiments, device memory 126 mayinclude one or more of protected data 126A and unprotected data 126B.Not all embodiments include each or both of these, but protected data126A and unprotected data 126B may be present in one or moreembodiments. Protected data 126A may include any data, including datastored on personal device 120, data for which personal device 120maintains at least partial control of, data for which personal device120 monitors or provides the ability to monitor, and the like, for whichsome form of authorization is required to access the data. Theauthorization may take any form and relate to any sub-unit, includingboth internally and externally to the device. For example, in anembodiment, protected data 126A may include data which is not availableto at least one application running on a computing device. For anotherexample, in an embodiment, protected data 126A may be available to oneapplication at any time, and to another application at specific times,or at times when the first application is not using the data. In anembodiment, protected data 126A includes data for which an applicationmust be authenticated (e.g., a Microsoft operating system certification,or a user flag set to true) in order to access the protected data 126A.

In an embodiment, protected data 126A includes data that a user, e.g.,user 105, cannot view until the user 105 verifies their identity, e.g.,through a password input or biometric identification. In an embodiment,protected data 126A is limited to the device, and is not transmitted toany other system not under the direct control of the personal device120. In an embodiment, protected data 126A is limited to the personaldevice 120, and only applications originating at the personal device120, or originating with the user 105, are allowed to read protecteddata 126A. In an embodiment, personal device 120 modifies or directs tobe modified protected data 126A, so at least a portion of the protecteddata 126A is altered or obscured. In an embodiment, personal device 120allows protected data 126A to be transmitted to an external entity underthe condition that the external entity will alter or obscure at least aportion of the protected data 126A.

Referring again to FIG. 1A, in an embodiment, personal device 120 mayinclude device memory 126, which, in some embodiments, may includeunprotected data 26B. In an embodiment, unprotected data 126B may haveno protections or limitations. In another embodiment, unprotected data126B may have protections and limitations, but be less protected and/orless limited than protected data 126B. In an embodiment, unprotecteddata 126B is broadcasted or otherwise transmitted upon request. In anembodiment, unprotected data 126B cannot be accessed by an entityexternal to personal device 120 due to device design or other factors,but there is no specific protection on unprotected data 126B from accessby one or more entities external to personal device 20.

Referring again to FIG. 1A, in an embodiment, personal device 120 mayinclude device interface component 128. In an embodiment, deviceinterface component 128 includes any component that allows the device tointeract with its environment. For example, in an embodiment, deviceinterface component 128 includes one or more sensors, e.g., a camera, amicrophone, an accelerometer, a thermometer, a satellite positioningsystem (SPS) sensor, a barometer, a humidity sensor, a compass, agyroscope, a magnetometer, a pressure sensor, an oscillation detector, alight sensor, an inertial measurement unit (IMU), a tactile sensor, atouch sensor, a flexibility sensor, a microelectromechanical system(MEMS), a radio, including a wireless radio, a transmitter, a receiver,an emitter, a broadcaster, and the like. In an embodiment, deviceinterface component 128 also may include one or more user interfacecomponents, e.g., user interface 122 (e.g., although they are drawnseparately, in some embodiments, user interface 122 is a type of deviceinterface component 128), and in some embodiments including one or moreuser input receiving components and output presenting components.

Referring again to FIG. 1A, in an embodiment, device interface component128 may include protected component 128A. Protected component 128A mayinclude any device interface component 128, of which some non-limitingexamples previously were enumerated, for which some form ofauthorization and/or authentication is required to access the data. Theauthorization may take any form and relate to any sub-unit, includingboth internally and externally to the device. In an embodiment,protected component 128A is similar to protected data 126A. For example,in an embodiment, a personal device 120, e.g., a smart phone, may havetwelve applications running on the smartphone. In an embodiment, six ofthose applications may have access to a protected component 128A, e.g.,a positioning sensor, and the other six may not. In some embodiments,data collected by a protected component 128A is part of the protectedcomponent 128A. In some embodiments, data collected by a protectedcomponent 128A becomes protected data 126A. In some embodiments, datacollected by a protected component 128A becomes protected data 126A someof the time, or none of the time. In some embodiments, data collected bya protected component 128A may be part of protected component 128A for aparticular amount of time, e.g., two weeks, and then may transition tounprotected data or data that is not considered protected orunprotected. In some embodiments, a protected component 128A may beaccessible to everyone at particular times and/or circumstances. Forexample, a protected component 128A, e.g., a wireless radio, may beaccessible to any entity between the hours of 7 and 8 pm, and onlyaccessible to specific entities and/or applications at other times. Insome embodiments, a protected component 128A, e.g., an image capturingcomponent, may be accessible to any entity when one or more conditionsare met, which conditions may or may not be related to the protectedcomponent 128A or the personal device 120, e.g., when the personaldevice 120 is at a particular location.

Referring again to FIG. 1A, in some embodiments, computing device 30 mayinclude personal device interface module 132. In some embodiments,personal device interface module 132 may communicate with one or morepersonal devices 120. In some embodiments, personal device interfacemodule 132 may receive data 131 received from a personal device 120.Acquired personal device data 131 may include any data gathered frompersonal device 120, in any manner. In some embodiments, computingdevice 30 may request data from personal device 120. In someembodiments, computing device 30 may receive data from personal device120 on a schedule. In some embodiments, computing device 130 mayretrieve data from personal device 120 when certain conditions are met.In some embodiments, personal device 120 is broadcasting data, andcomputing device 130 gathers the broadcasted data. In some embodiments,personal device 120 broadcasts data that only computing device 130 canuse (e.g., decrypt, interpret, or the like). In some embodiments,personal device 120 may transmit acquired personal device data 131 tocomputing device 30 using one or more communication networks 140, whichwill be described in more detail herein.

Referring again to FIG. 1A, in some embodiments, the acquired personaldevice data 131 may be anonymous data 131A. In an embodiment, anonymousdata refers to data from which the origin of the data cannot be uniquelyidentified. In some embodiments, the origin of the data may refer to thepersonal device 120, e.g., a unique identifier, e.g., a MAC address. Insome embodiments, the origin of the data may refer to a user 105associated with the data, either through ownership, use, or otherrelationship with the device, e.g., a username, a user's name, or auser's social security or other identifying number, or network addressor identification. It is noted that, in some embodiments, the device maybe able to recognize the origin of the data, e.g., an identity ofpersonal device 120, that is transmitting the data due to the nature ofthe data transmission, but be unable to deduce the origin of the datathrough the data itself, in which case, in some embodiments, this datais still considered anonymous data 131A.

Anonymous data 131A may include data for which uniquely identifyinginformation has been removed, or data for which uniquely identifyinginformation has been concealed, obscured, made uncertain, madeambiguous, screened, camouflaged, masked, veiled, shrouded, hidden,encoded, encrypted, or otherwise altered. In some embodiments, thereceived anonymous data 131A never included uniquely identifyinginformation. In some embodiments, anonymous data 131A may partially oridentify its origin in a manner that is not unique, e.g., the user 105or the personal device 120 from which the anonymous data originated. Insome embodiments, uniquely identifying information may be extracted fromanonymous data 131A using additional information, e.g., a lookup table,hash, or other known algorithm. In some embodiments, uniquelyidentifying information may be deduced from anonymous data 131A withoutadditional information. In some embodiments, uniquely identifyinginformation may not be retrieved from anonymous data 131A once the datais in its anonymous format.

In an embodiment, acquired personal device data 131 may includenon-anonymous data 131B. In some embodiments, non-anonymous data 131Bmay identify, either explicitly or implicitly, the origin of the data.In some embodiments, the origin of the data may refer to the personaldevice 120, e.g., a unique identifier, e.g., a MAC address. In someembodiments, the origin of the data may refer to a user 105 associatedwith the data, either through ownership, use, or other relationship withthe device, e.g., a username, a user's name, or a user's social securityor other identifying number, or network address or identification.

Referring to FIGS. 1A-1D, in an embodiment, computing device 130 mayinclude a data anonymizer module 134A that converts non-anonymous data131B into anonymized data, in a process described in more detail withrespect to FIGS. 1C and 1D. In an embodiment, depending on the type ofanonymization, there may be additional data that can be used to returnthe anonymized data into non-anonymous data, e.g., a lookup table. Insome such embodiments, the additional data, e.g., de-anonymization data,may be stored in data de-anonymization information storing module 135.

Referring again to FIGS. 1A-1D, in an embodiment, computing device 130may include a data obscuring module 134B. For example, in an embodiment,data obscuring module 134B may obscure the non-anonymous data 131B,similarly to the data anonymizer module 134A. For example, in anembodiment, data obscuring module 134B may apply data masking. In anembodiment, data obscuring module 134B may obscure by addition, e.g., byadding false identification information to the true identificationinformation, so that the false identification information may not bedistinguished from the true identification information. Datade-anonymization information storing module 135, data anonymizer module134A, and data obscuring module 134B may be absent in some embodiments.

Referring again to FIG. 1A, in an embodiment, computing device 130 mayinclude service developer interface module 136. Service developerinterface module 136 may communicate with service developer 160, e.g.,via communication network 140. Specifically, in an embodiment, servicedeveloper interface module 136 may provide limited information regardingthe acquired personal device data 131. In an embodiment, for example,service developer interface module 136 may provide information toservice developer 160 regarding the type of data collected. In anembodiment, for example, service developer interface module 136 mayprovide information to service developer 160 regarding an aggregatesynopsis of the data collected. In an embodiment, service developer 160may receive such information and make a decision about what types ofservices to develop, e.g., using development decision module 162.

Referring again to FIG. 1A, in an embodiment, computing device 130 mayinclude service provider interface module 138. In an embodiment, serviceprovider interface module 138 may communicate with service provider 170,e.g., via communication network 140.

In an embodiment, service provider interface module 138 may include datarights management module 138A. In an embodiment, data rights managementmodule 138A may keep track of which services have rights to whichpersonal device data. For example, in an embodiment, service 172A mayhave rights to certain anonymous data 131A. For another example, in anembodiment, service 172B may have rights to data that has been processedthrough the data anonymizer 134A.

Referring again to FIG. 1A, in an embodiment, service provider interfacemodule 138 may include service information module 138B. Serviceinformation module 138B may include a list of services that are providedfrom service provider 170, so that such information may be delivered topersonal device 120, in an embodiment. In an embodiment, computingdevice 130 may present one or more of the services listed in serviceinformation module 138B to personal device 120, either upon request, orupon detecting that personal device 120 may be interested in one or moreof the services.

Referring again to FIG. 1A, in an embodiment, service provider 170 mayprovide services to a personal device 120. In an embodiment, theseservices may be delivered to directly to personal device 120. In anembodiment, service provider 170 has limited or no communication withpersonal device 120, and communication is handled through anintermediary, e.g., computing device 130. In an embodiment, computingdevice 130 handles the delivery of services and data between serviceprovider 170 and personal device 120 such that protected data 126A andprotected component 128A are protected from service provider 170, butthat service provider 170 can still provide services, e.g., service 172Aand service 172B, to personal device 120. In an embodiment, serviceprovider 170 includes a list of services management module 174 thatmaintains a list of services to present to computing device 130, e.g.,to allow service information module 138B of computing device 130 tomaintain information about various services.

In various embodiments, the communication network 140 may include one ormore of a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a wireless local area network (WLAN), apersonal area network (PAN), a Worldwide Interoperability for MicrowaveAccess (WiMAX), public switched telephone network (PTSN), a generalpacket radio service (GPRS) network, a cellular network, and so forth.The communication networks 140 may be wired, wireless, or a combinationof wired and wireless networks. It is noted that “communication network”as used herein and in the drawings refers to one or more communicationnetworks, which may or may not interact with each other and which, insome embodiments, may work in concert, wittingly or unwittingly, tofacilitate communication between one or more entities.

Referring now to FIG. 1C, an embodiment may include a personal device120A and a personal device 120B. Personal device 120A may generatenon-anonymous data 144A, and personal device 120B may generatenon-anonymous data 144B. Non anonymous data 144A and non-anonymous data144B may be transmitted to computing device 130A, which may be anon-exclusive and non-limiting example of computing device 130. In anembodiment, computing device 130A may include a data anonymizer module134A. In an embodiment, data anonymizer module 134A may includeirreversible anonymizer module 137A, which generates anonymous data thatis irreversible, e.g., in an example, the identifying data has beenremoved. In an embodiment, data anonymizer module 134A may includecollective anonymizer module 137B, which may take the non-anonymous data144A and the non-anonymous data 144B and create an aggregated, generalanonymous data, as shown FIG. 1C. In an embodiment, data anonymizermodule 134A may include reversible anonymizer module 137C, which may usea private lookup table 135A to convert the non-anonymous data intoanonymous data. In an embodiment, that private lookup table 135A may bestored in the data-deanonymization information storing module 135.

Referring now to FIG. 1D, in an embodiment, a computing device 130B mayhave a data anonymizer 134A that may apply an anonymizing function 132A,as shown in FIG. 1D. For example, an anonymizing function may use acryptographic method, a perturbation method, a DataFly algorithm,top-down specialization, and/or Mondarian multi-dimensional k-anonymity,as non-limiting and non-exclusive examples. In another embodiment, adata obscuring module 134B obscures the non-anonymous data. In anembodiment, the obscuring may be accomplished by adding similar-lookingand plausible “false” data to the actual identifying data, so thatlater, the true data cannot be determined merely by looking at the data.In an embodiment, the anonymized data may be used by the serviceprovider interface module 38 to give data to the service provider 170,either to carry out a portion of a service, or to determine whichservices may be useful to one or more personal devices 120.

The examples shown in FIGS. 1C and 1D are merely examples of how a dataanonymizer might be implemented, and are not intended to be limiting orexclusive. There are many other techniques for anonymizing the data,some of which will be mentioned herein.

Referring again to FIG. 1B, FIG. 1B shows a more detailed description ofcomputing device 130. In an embodiment, computing device 130 may includea processor 132. Processor 132 may include one or more microprocessors,Central Processing Units (“CPU”), a Graphics Processing Units (“GPU”),Physics Processing Units, Digital Signal Processors, Network Processors,Floating Point Processors, and the like. In some embodiments, processor132 may be a server. In some embodiments, processor 132 may be adistributed-core processor. Although processor 132 is as a singleprocessor that is part of a single personal device 120, processor 132may be multiple processors distributed over one or many computingdevices 30, which may or may not be configured to operate together.Processor 132 is illustrated as being configured to execute computerreadable instructions in order to execute one or more operationsdescribed above, and as illustrated in FIGS. 5, 6A-6F, 7A-7I, and 8A-8B.In some embodiments, processor 132 is designed to be configured tooperate as processing module 150, which may include one or more of datarelated to a device having a particular protected portion for which thedevice controls access acquiring module 152, presentation of a proposalto assist in performing at least one device-related service in returnfor access to the device particular protected portion facilitatingmodule 154, and performance of at least a portion of the one or moreservices facilitating in response to a grant of access to data acquiredby the device module 154.

In an embodiment, computing device 130 may include a memory 133. In someembodiments, memory 133 may comprise of one or more of one or more massstorage devices, read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), cache memorysuch as random access memory (RAM), flash memory, synchronous randomaccess memory (SRAM), dynamic random access memory (DRAM), and/or othertypes of memory devices. In some embodiments, memory 133 may be locatedat a single network site. In some embodiments, memory 133 may be locatedat multiple network sites, including sites that are distant from eachother.

Referring now to FIG. 2, FIG. 2 illustrates an exemplary implementationof the identifying one or more services configured to carry out at leastone task for a device, the identifying at least partly based on devicedata module 152. As illustrated in FIG. 2, the identifying one or moreservices configured to carry out at least one task for a device, theidentifying at least partly based on device data module 152 may includeone or more sub-logic modules in various alternative implementations andembodiments. For example, as shown in FIG. 2, e.g., FIG. 2A, in someembodiments, module 152 may include one or more of identifying anotification presentation service configured to notify when one or moreentities are within a particular proximity to the device, theidentifying at least partly based on device data module 202 andidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on device datato which limited access is provided module 208. In some embodiments,module 202 may include one or more of identifying a notificationpresentation service configured to notify when one or more entities arewithin a particular proximity to the device, the identifying at leastpartly based on data indicating the device has a large contact listmodule 204 and identifying a notification presentation serviceconfigured to notify when one or more entities are within a particularproximity to the device, the identifying at least partly based on dataindicating that a device contact list has restricted access module 206.In some embodiments, module 208 may include one or more of identifyingone or more services configured to carry out at least one task for adevice, the identifying at least partly based on device data to whichlimited access is provided to one or more programs module 210 andidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on device datato which limited access is provided to a kernel-level program module214. In some embodiments, module 210 may include depicting identifyingone or more position-dependent services configured to carry out at leastone task for a device, the identifying at least partly based on devicedata to which limited access is provided to one or more augmentedreality programs module 212.

Referring again to FIG. 2, e.g., FIG. 2B, in some embodiments, module152 may include one or more of identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device sensor data module 216 and identifyingone or more services configured to carry out at least one task for adevice, the identifying at least partly based on device data to whichaccess is restricted from one or more external entities module 226. Insome embodiments, module 216 may include one or more of identifying oneor more services configured to carry out at least one task for a device,the identifying at least partly based on device image capturing sensordata module 218 and identifying one or more services configured to carryout at least one task for a device, the identifying at least partlybased on device sensor data module 222. In some embodiments, module 218may include identifying one or image processing services configured tocarry out at least one task for a device, the identifying at leastpartly based on device image capturing sensor data module 220. In someembodiments, module 222 may include identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device sensor data to which access isrestricted to at least a portion of the device module 224. In someembodiments, module 226 may include one or more of identifying one ormore services configured to carry out at least one task for a device,the identifying at least partly based on device data to which access isrestricted from a communication network provider module 228, identifyingone or more services configured to carry out at least one task for adevice, the identifying at least partly based on device data to whichaccess is restricted from a device manufacturer module 230, andidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on device datato which access is restricted from a device application producer module232. In some embodiments, module 232 may include identifying one or moreservices, the identifying at least partly based on device data to whichaccess is restricted from a device operating system producer module 234.

Referring again to FIG. 2, e.g., FIG. 2C, in some embodiments, module152 may include identifying one or more services configured to carry outat least one task for a device, the identifying at least partly based ondevice property data module 236. In some embodiments, module 236 mayinclude identifying one or more services from one or more serviceprovider provided available services configured to carry out at leastone task for a device, the identifying at least partly based on deviceproperty data module 238. In some embodiments, module 238 may includeidentifying one or more services from two or more available servicesprovided by two or more discrete service providers, said one or moreservices configured to carry out at least one task for a device, theidentifying at least partly based on device property data module 240. Insome embodiments, module 240 may include identifying one or moreservices from two or more available services provided by two or morediscrete service providers, said one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device property data and partly based on one or moreservice provider properties module 242. In some embodiments, module 242may include one or more of identifying one or more services from two ormore available services provided by two or more discrete serviceproviders, said one or more services configured to carry out at leastone task for a device, the identifying at least partly based on deviceproperty data and partly based on service provider priority listplacement module 244 and identifying one or more services from two ormore available services provided by two or more discrete serviceproviders, said one or more services configured to carry out at leastone task for a device, the identifying at least partly based on deviceproperty data and partly based on service provider history with devicemodule 246. In some embodiments, module 246 may include identifying oneor more services from two or more available services provided by two ormore discrete service providers, said one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device property data and partly based on serviceprovider previously providing service to device module 248.

Referring again to FIG. 2, e.g., FIG. 2D, as described above, in someembodiments, module 152 may include module 236, module 236 may includemodule 238, module 238 may include module 240, module 240 may includemodule 242, and module 242 may include module 246. In some embodiments,module 246 may include identifying one or more services from two or moreavailable services provided by two or more discrete service providers,said one or more services configured to carry out at least one task fora device, the identifying at least partly based on device property dataand partly based on the service provider providing the one or moreidentified services to a different device having a common characteristicwith the device module 250. In some embodiments, module 242 may includeidentifying one or more services from two or more available servicesprovided by two or more discrete service providers, said one or moreservices configured to carry out at least one task for a device, theidentifying at least partly based on device property data and partlybased on service provider data sharing agreement module 252.

Referring again to FIG. 2, e.g., FIG. 2E, as described above, in someembodiments, module 152 may include module 236, module 236 may includemodule 238, module 238 may include module 240, and module 240 mayinclude module 242. In some embodiments, module 242 may includeidentifying one or more services from two or more available servicesprovided by two or more discrete service providers, said one or moreservices configured to carry out at least one task for a device, theidentifying at least partly based on device property data and partlybased on service provider prior contract module 254.

Referring again to FIG. 2, e.g., FIG. 2F, in some embodiments, module152 may include identifying one or more services configured to carry outat least one task for a device, the identifying at least partly based ondevice usage information data module 256. In some embodiments, module256 may include one or more of identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device position history information module 258,identifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on deviceapplication usage information data module 262, identifying one or moreservices configured to carry out at least one task for a device, theidentifying at least partly based on device web browsing informationdata module 264, and identifying one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on particular application usage time amount data module268. In some embodiments, module 258 may include identifying a caloricintake service configured to carry out at least one task for a device,the identifying at least partly based on device position historyinformation module 260. In some embodiments, module 264 may includeidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on device webbrowsing information indicating three or more downloads a day from bankaccount websites data module 266. In some embodiments, module 268 mayinclude identifying one or more game playing services configured tocarry out at least one task for a device, the identifying at leastpartly based on particular game usage time amount greater than aparticular amount module 270.

Referring again to FIG. 2, e.g., FIG. 2G, in some embodiments, module152 may include one or more of identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device data transmission amount module 272,identifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on restricteddevice data inventory module 274, and identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on restricted device sensor module 280. In someembodiments, module 274 may include one or more of identifying one ormore services configured to carry out at least one task for a device,the identifying at least partly based on restricted device datainventory indicating restricted position data module 276 and identifyingone or more services configured to carry out at least one task for adevice, the identifying at least partly based on restricted device datainventory indicating a number of stored previous locations and a numberof stored previous contacts module 278. In some embodiments, module 280may include one or more of identifying one or more data traffic analysisservices configured to carry out at least one task for a device, theidentifying at least partly based on a restricted data radio module 282and identifying one or more weather analysis services configured tocarry out at least one task for a device, the identifying at leastpartly based on a restricted barometric pressure sensor module 284.

Referring again to FIG. 2, e.g., FIG. 2H, in some embodiments, module152 may include identifying one or more alert services configured toalert when one or more devices controlled by a person in the devicecontact list is within a particular proximity to the device, theidentifying at least partly based on device data module 286.

Referring now to FIG. 3, FIG. 3 illustrates an exemplary implementationof access to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingmodule 154. As illustrated in FIG. 3, the access to data acquired by thedevice as negotiated result of facilitating a providing of one or moreidentified services requesting module 154 may include one or moresub-logic modules in various alternative implementations andembodiments. For example, as shown in FIG. 3 (e.g., FIG. 3A), in someembodiments, module 154 may include access to data acquired by one ormore device sensors as negotiated result of facilitating a providing ofone or more identified services requesting module 302. In someembodiments, module 302 may include access to data acquired by one ormore device positioning sensors as negotiated result of facilitating aproviding of one or more identified services requesting module 304. Insome embodiments, module 304 may include access to data acquired by oneor more device positioning sensors as negotiated result of facilitatinga providing of an identified position-based service requiring access tothe data acquired by the one or more device positioning sensorsrequesting module 306. In some embodiments, module 306 may includeaccess to position data acquired by one or more device positioningsensors and stored on the device as negotiated result of facilitating aproviding of an identified position-based service requiring access tothe data acquired by the one or more device positioning sensorsrequesting module 308. In some embodiments, module 308 may includeaccess to position data acquired by one or more device positioningsensors and stored on the device as negotiated result of facilitating aproviding of an identified entity proximity alarm based servicerequiring access to the data acquired by the one or more devicepositioning sensors requesting module 310. In some embodiments, module310 may include access to position data acquired by one or more devicepositioning sensors and stored on the device as negotiated result oftransmitting, to the device, an identified entity proximity alarm basedservice requiring access to the data acquired by the one or more devicepositioning sensors requesting module 312.

Referring again to FIG. 3, e.g., FIG. 3B, in some embodiments, module154 may include access to data acquired by the device as negotiatedresult of facilitating a providing of one or more identified servicesrequesting from the device module 314. In some embodiments, module 314may include one or more of access to data acquired by the device asnegotiated result of facilitating a providing of one or more identifiedservices requesting from an access control application of the devicemodule 316 and access to data acquired by the device as negotiatedresult of facilitating a providing of one or more identified servicesrequesting from the device that has user preauthorization to grant ordeny access according to one or more particular conditions module 318.In some embodiments, module 318 may include one or more of access todata acquired by the device as negotiated result of facilitating aproviding of one or more identified services requesting from the devicethat has user preauthorization to grant or deny access according to aservice application author identity module 320, access to data acquiredby the device as negotiated result of facilitating a providing of one ormore identified services requesting from the device that has userpreauthorization to grant access to one or more applications having acommon author entity as one or more applications previously operated bythe device module 322, and access to data acquired by the device asnegotiated result of facilitating a providing of one or more identifiedservices requesting from the device that has user preauthorization togrant or deny access according to a type of data requested by the one ormore services module 324.

Referring again to FIG. 3, e.g., FIG. 3C, in some embodiments, module154 may include one or more of access to data acquired by the device asnegotiated result of facilitating a providing of one or more identifiedservices requesting from device operator module 326 and facilitation ofuser interaction regarding access to data acquired by the device asnegotiated result of facilitating a providing of one or more identifiedservices requesting module 332. In some embodiments, module 326 mayinclude access to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requesting,via the device, from device operator module 328. In some embodiments,module 328 may include access to data acquired by the device asnegotiated result of providing of one or more identified servicesrequesting, by instructing device to carry out user interactionoperations, from device operator module 330. In some embodiments, module332 may include one or more of transmission of instructions to proceedwith a user interaction regarding access to data acquired by the deviceas negotiated result of facilitating a providing of one or moreidentified services requesting module 334, transmission of anapplication that executes a user interaction regarding access to dataacquired by the device as negotiated result of facilitating a providingof one or more identified services requesting module 336, andfacilitation of presentation of request for access to data acquired bythe device as negotiated result of facilitating a providing of one ormore identified services requesting module 338. In some embodiments,module 338 may include facilitation of display of request for access todata acquired by the device as negotiated result of facilitating aproviding of one or more identified services requesting module 340. Insome embodiments, module 340 may include one or more of facilitation ofdisplay of request for access to data acquired by the device as apayment for facilitation of providing of one or more identified servicesrequesting module 342 and facilitation of display of request for accessto data acquired by the device as a necessary condition precedent tofacilitation of providing of one or more identified services requestingmodule 344.

Referring again to FIG. 3, e.g., FIG. 3E, in some embodiments, module154 may include one or more of presentation of an example of providingthe one or more services facilitating module 346 and presentation of arequest for access to the data acquired by the device as a manner ofcarrying out the one or more services as shown in the presentation ofthe example facilitating module 348. In some embodiments, module 348 mayinclude one or more of presentation of a request for access to the dataacquired by the device as a necessary condition of carrying out the oneor more services as shown in the presentation of the examplefacilitating module 350 and presentation of a request for access to thedata acquired by the device as a terms of service agreement for carryingout the one or more services as shown in the presentation of the examplefacilitating module 352.

Referring now to FIG. 4, FIG. 4 illustrates an exemplary implementationof the provision of at least a portion of the one or more servicesfacilitating upon receipt of negotiated access to data acquired by thedevice module 156. As illustrated in FIG. 4, the provision of at least aportion of the one or more services facilitating upon receipt ofnegotiated access to data acquired by the device module 156 may includeone or more sub-logic modules in various alternative implementations andembodiments. For example, as shown in FIG. 4, e.g., FIG. 4A, in someembodiments, module 156 may include one or more of provision of at leasta portion of the one or more services facilitating upon receipt ofnegotiated access to data previously acquired by the device module 402,provision of at least a portion of the one or more services facilitatingupon receipt of negotiated access to data as it is obtained by thedevice module 404, provision of at least a portion of the one or moreservices facilitating upon receipt of negotiated access to data after itis obtained by the device module 406, provision of at least a portion ofthe one or more services facilitating upon receipt of negotiated accessto data obtained by a device environment interaction component module408, and providing a location at which one or more applicationsconfigured to perform one or more services are configured to bedownloaded upon receipt of negotiated access to data acquired by thedevice module 410.

Referring again to FIG. 4, e.g., FIG. 4B, in some embodiments, module156 may include provision of at least a portion of a physical activitytracker service facilitating upon receipt of negotiated access to dataacquired by the device module 412. In some embodiments, module 412 mayinclude one or more of facilitating a download of an applicationconfigured to carry out at least a portion of a physical activitytracker service upon receipt of negotiated access to data acquired bythe device module 414 and providing access to a repository configured toreceive data related to the physical activity tracker service uponreceipt of negotiated access to data acquired by the device module 416.In some embodiments, module 416 may include one or more of providingaccess to a data repository configured to receive data related to thephysical activity tracker service upon receipt of negotiated access toacceleration data acquired by a device accelerometer module 418 andproviding access to a data repository configured to receive data relatedto the physical activity tracker service upon receipt of negotiatedaccess to activity name inputted to the device by a user and stored inthe device module 420.

Following are a series of flowcharts depicting implementations. For easeof understanding, the flowcharts are organized such that the initialflowcharts present implementations via an example implementation andthereafter the following flowcharts present alternate implementationsand/or expansions of the initial flowchart(s) as either sub-componentoperations or additional component operations building on one or moreearlier-presented flowcharts. Those having skill in the art willappreciate that the style of presentation utilized herein (e.g.,beginning with a presentation of a flowchart(s) presenting an exampleimplementation and thereafter providing additions to and/or furtherdetails in subsequent flowcharts) generally allows for a rapid and easyunderstanding of the various process implementations. In addition, thoseskilled in the art will further appreciate that the style ofpresentation used herein also lends itself well to modular and/orobject-oriented program design paradigms.

Further, in FIG. 5 and in the figures to follow thereafter, variousoperations may be depicted in a box-within-a-box manner. Such depictionsmay indicate that an operation in an internal box may comprise anoptional example embodiment of the operational step illustrated in oneor more external boxes. However, it should be understood that internalbox operations may be viewed as independent operations separate from anyassociated external boxes and may be performed in any sequence withrespect to all other illustrated operations, or may be performedconcurrently. Still further, these operations illustrated in FIG. 5 aswell as the other operations to be described herein may be performed byat least one of a machine, an article of manufacture, or a compositionof matter.

Referring now to FIG. 5, FIG. 5 shows operation 500, which may includeoperation 502 depicting identifying one or more services configured tobe provided to a user of a device, said identifying at least partlybased on data regarding one or more properties of the device. Forexample, FIG. 1, e.g., FIG. 1B, shows data related (e.g., related in anyway, regardless of how tenuous, e.g., in the example listed herein, theservice is related because there is a contact list present on thesmartphone, which for purposes of an embodiment of this application, ismore than sufficient to establish “related”) to a device (e.g., a user'stablet device) having a particular protected portion for which thedevice controls access acquiring module 152 identifying (e.g., finding,selecting, choosing, receiving, acquiring, retrieving, picking up,creating, generating, intercepting, reading, hearing, detecting,picking, weighting, and the like) one or more services (e.g., a “whereare your friends” service that shows a user of a device where the user'sfriends, e.g., the people listed in the user's contact list, arelocated) configured to be provided (e.g., configured to be madeavailable to, regardless of actual use) to a user of a device (e.g., asmartphone), said identifying (e.g., finding, selecting, choosing,receiving, acquiring, retrieving, picking up, creating, generating,intercepting, reading, hearing, detecting, picking, weighting, and thelike) at least partly based on data regarding (e.g., data about anyaspect, whether temporary or permanent, or whether related to theenvironment) one or more properties (e.g., any information, regardlessof context dependency, triviality, or other factor) of the device (e.g.,a user's tablet device).

Referring again to FIG. 5, operation 500 may include operation 504depicting requesting access to data collected by one or more portions ofthe device, in exchange for providing at least a portion of one of theone or more identified services. For example, FIG. 1, e.g., FIG. 1B,shows presentation of a proposal to assist in performing at least onedevice-related service in return for access to the device particularprotected portion facilitating module 154 requesting access (e.g., thegiving of one or more authentication tools, e.g., passwords, privileges,logins, addresses, and the like, or permission, authorization,authentication, and the like to one or more of reading, writing,modifying, altering, deleting, encrypting, transmitting, receiving, orperforming any of one or more actions or operations upon) to datacollected (e.g., received, retrieved, or generated by any interface,including input and/or output devices, e.g., keyboards and pointingdevices, and one or more sensors, alone or in concert) by one or moreportions (e.g., any component, including hardware, software, firmware,API, and any combination of the foregoing) of the device (e.g., theuser's tablet device) in exchange (e.g., in bargain for, in deal for, intrade for, in consideration of, as a quid pro quo, and the like) forproviding (e.g., taking one or more actions that, whether directly orindirectly, are intended to assist in the completion, execution, orcarrying out of at least a portion of, regardless of whether suchactions constitute the whole of the service or only a part of) at leastone of the one or more identified services (e.g., a “where are yourfriends” service that shows a user of a device where the user's friends,e.g., the people listed in the user's contact list, are located).

Referring again to FIG. 5, operation 500 may include operation 506depicting providing at least a portion of the one or more services afterreceiving access to the data collectable by one or more portions of thedevice. For example. FIG. 1, e.g., FIG. 1B, shows performance of atleast a portion of the one or more services facilitating in response toa grant of access to data acquired by the device module 156 providinge.g., taking one or more actions that, whether directly or indirectly,are intended to assist in the completion, execution, or carrying out ofone or more steps or instructions in executing or carrying out) of atleast a portion of the at least one service (e.g., the “where are theuser's friends” service) after receiving access (e.g., the giving of oneor more authentication tools, e.g., passwords, privileges, logins,addresses, and the like, or permission, authorization, authentication,and the like to one or more of reading, writing, modifying, altering,deleting, encrypting, transmitting, receiving, or performing any of oneor more actions or operations upon) to the data (e.g., the user'scontact list stored on the tablet device) collectable by one or moreportions (e.g., the on-screen virtual keyboard of the tablet device) ofthe device (e.g., the user's tablet device).

FIGS. 6A-6E depict various implementations of operation 502, depictingidentifying one or more services configured to be provided to a user ofa device, said identifying at least partly based on data regarding oneor more properties of the device according to embodiments. Referring nowto FIG. 6A, operation 502 may include operation 602 depictingidentifying a service configured to present a notification when one ormore entities listed in the device's contact list are within aparticular proximity to the user of the device, said identifying atleast partly based on data regarding one or more properties of thedevice. For example, FIG. 2, e.g., FIG. 2A, shows identifying a servicenotification presentation service configured to notify when one or moreentities are within a particular proximity to the device, theidentifying at least partly based on device data module 202 identifying(e.g., selecting, choosing, retrieving, requesting from third partiesand selecting from the responses, selecting from a list, selecting froma database, selecting based on one or more criteria, and the like, oneor more of) a service configured to present a notification (e.g., lightup a light, or present a message on a screen) when one or more entitieslisted in the device's contact list are within a particular proximity tothe user of the device (e.g., within 30 feet of), said identifying atleast partly based on data regarding one or more properties of thedevice (e.g., based on data indicating a position of the device,granular within a city block).

Referring again to FIG. 6A, operation 602 may include operation 604depicting identifying a service configured to present a notificationwhen one or more people listed in the device's contact list are within aparticular proximity to the user of the device, said identifying atleast partly based on a device storing a large contact list. Forexample, FIG. 2, e.g., FIG. 2A, shows identifying a notificationpresentation service configured to notify when one or more entities arewithin a particular proximity to the device, the identifying at leastpartly based on data indicating the device has a large contact listmodule 204 identifying a service configured to present a notification(e.g., making an audible sound) when one or more people listed in thedevice's contact list are within a particular proximity to a user of thedevice (e.g., within one mile), said identifying at least partly basedon a device storing a large contact list (e.g., the service is selectedbecause someone with a large contact list might want to know when acertain contact or group of contacts is close to her location).

Referring again to FIG. 6A, operation 602 may include operation 606depicting identifying a service configured to present a notificationwhen one or more people listed in the device's contact list are within aparticular proximity to the user of the device, said identifying atleast partly based on a restricted-access contact list stored on thedevice. For example, FIG. 2, e.g., FIG. 2A, shows identifying anotification presentation service configured to notify when one or moreentities are within a particular proximity to the device, theidentifying at least partly based on data indicating that a devicecontact list has restricted access module 206 identifying a serviceconfigured to present a notification when one or more people listed inthe device's contact list are within a particular proximity (e.g.,thirty feet) to the user of the device (e.g., a smartphone, e.g., aSamsung Galaxy), said identifying at least partly based on arestricted-access contact list stored on the device (e.g., the serviceof presenting notifications when contact list contacts are within aparticular proximity is selected because the device, e.g., the SamsungGalaxy, has restricted access to its contact list from outside entities,and this service is a manner in which access may be granted).

Referring again to FIG. 6A, operation 502 may include operation 608depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on datastored on the device to which at least a portion of the device haslimited or no access. For example, FIG. 2, e.g., FIG. 2A, showsidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on device datato which limited access is provided module 208 identifying one or moreservices (e.g., an alternate health-food finding service) configured tobe provided to a user of a device (e.g., a smart appliance in a user'shouse, e.g., a refrigerator), said identifying at least partly based ondata stored on the device (e.g., an updating inventory of what is in therefrigerator stored on the device, which has access to the things thatthe user bought with a credit card that are perishable) to which atleast a portion of the device has limited or no access (e.g., the datatransmission portion of the smart refrigerator may not have access tothe refrigerator inventory).

Referring again to FIG. 6A, operation 608 may include operation 610depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on datastored on a device to which at least one application of the device haslimited or no access. For example, FIG. 2, e.g., FIG. 2A, showsidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on device datato which limited access is provided to one or more programs module 210identifying one or more services (e.g., an ice-cream shop locatingservice) configured to be provided to a user of a device (e.g., a tabletdevice, e.g., an iPad), said identifying at least partly based on datastored on a device to which at least one application of the device(e.g., an application installed by the device operating system designer,which also designed the ice cream shop locating service) has limited orno access (e.g., access is allowed only to the applications that theuser specifically enumerates).

Referring again to FIG. 6A, operation 610 may include operation 612depicting identifying a location-dependent service configured to beprovided to a user of the device, said identifying at least partly basedon previous location data stored on the device, to which one or moregame applications of the device have limited or no access. For example,FIG. 2, e.g., FIG. 2A, shows identifying one or more position-dependentservices configured to carry out at least one task for a device, theidentifying at least partly based on device data to which limited accessis provided to one or more augmented reality programs module 212identifying a location-dependent service (e.g., a service to show theaverage strength of wireless signals in the vicinity of the device)configured to be provided to a user of a device (e.g., a cellulartelephone), said identifying at least partly based on previous locationdata stored on the device, to which one or more game applications of thedevice (e.g., the Brick Breaker game designed for Blackberry) havelimited or no access (e.g., that application cannot access the locationinformation, or the wireless radio).

Referring again to FIG. 6A, operation 608 may include operation 614depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on datastored on the device to which an operating system of the device haslimited or no access. For example, FIG. 2, e.g., FIG. 2A, showsidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on device datato which limited access is provided to a kernel-level program module 214identifying one or more services (e.g., a new music identifying service)configured to be provided to a user of a device, said identifying atleast partly based on data stored on the device (e.g., the identifyingof the application is partly based on the songs that are stored on thedevice, and partly based on the recognition that more than 70% of thedevice's memory is unused) to which an operating system of the devicehas limited or no access (e.g., the operating system of the device hasaccess to the information regarding usage of the device memory, but notaccess to the names of all the songs accessible through the device).

Referring now to FIG. 6B, operation 502 may include operation 616depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on dataregarding one or more sensors of the device. For example, FIG. 2, e.g.,FIG. 2B, shows identifying one or more services configured to carry outat least one task for a device, the identifying at least partly based ondevice sensor data module 216 identifying one or more services (e.g., aservice designed to predict the best time of day to go for a bicycleride) configured to be provided to a user of a device, said identify

Referring again to FIG. 6B, operation 616 may include operation 618depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on dataregarding an image capturing sensor of the device. For example, FIG. 2,e.g., FIG. 2B, shows identifying one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device image capturing sensor data module 218identifying one or more services (e.g., a service showing the user ofthe device a list of one or more upcoming concerts that could beattended, based on music that has been played on the device)

Referring again to FIG. 6B, operation 618 may include operation 620depicting identifying an image-recognition service configured to beprovided to a user of the device, said identifying at least partly basedon data regarding an image capturing sensor of the device. For example,FIG. 2, e.g., FIG. 2B, shows identifying one or image processingservices configured to carry out at least one task for a device, theidentifying at least partly based on device image capturing sensor datamodule 220 identifying an image-recognition service configured to beprovided to a user of a device (e.g., a wireless-radio enabled digitalSLR camera), said identifying at least partly based on data regarding animage capturing sensor of the device (e.g., the service is only providedto digital cameras having image capturing sensors with greater capacitythan five megapixels).

Referring again to FIG. 6B, operation 616 may include operation 622depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on dataindicating restricted access to one or more sensors of the device. Forexample, FIG. 2, e.g., FIG. 2B, shows identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on restricted device sensor data module 222identifying one or more services (e.g., a service that identifies whichtime of day is best to run on one or more particular roads) configuredto be provided to a user of the device (e.g., a tablet device, e.g., aSamsung Galaxy), said identifying at least partly based on dataindicating restricted access (e.g., one or more entities cannot accesssomething without one or more additional steps) to one or more sensorsof the device (e.g., Bluetooth radio).

Referring again to FIG. 6B, operation 622 may include operation 624depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on dataindicating that one or more portions of the device do not have access toone or more sensors of the device. For example, FIG. 2, e.g., FIG. 2B,shows identifying one or more services configured to carry out at leastone task for a device, the identifying at least partly based on devicesensor data to which access is restricted to at least a portion of thedevice module 224 (e.g., a service that identifies which time of day isbest to go for a run based on the weather patterns for that day)configured to be provided to a user of the device, said identifying atleast partly based on data indicating that one or more portions of thedevice (e.g., an application installed by the user that has access tothe user's contact list but not access to the barometer) do not haveaccess to one or more sensors of the device (e.g., the barometer, andthe application wants access to the barometer sensor, so the weatherpattern based service is identified).

Referring again to FIG. 6B, operation 502 may include operation 626depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on datastored on the device to which one or more entities external to thedevice have limited or no access. For example, FIG. 2, e.g., FIG. 2B,shows identifying one or more services configured to carry out at leastone task for a device, the identifying at least partly based on devicedata to which access is restricted from one or more external entitiesmodule 226 identifying one or more services (e.g., a service thatidentifies how far an athlete should run on a particular day, based onthe length and speed of the runs on previous days that are stored on thedevice) configured to be provided to a user of the device (e.g., auser's smartphone, e.g., a Nokia Lumia Windows phone), said identifyingat least partly based on data stored on the device (e.g., data regardinga user's last twenty web searches) to which one or more entities (e.g.,a communication network provider that provides one or more networks forthe device to communicate on) external to the device (e.g., the servicedoes not originate from the device, but from a tower or other structurethat is not part of the device) have limited or no access (e.g., thecommunication network provider can only access one of the twenty websearches, e.g., the most recent one, but the communication networkprovider wants access to all of them, e.g., this shows that there maynot be a direct, immediately obvious link between the informationdesired by the entity and the offered service, although that may be thecase in other embodiments).

Referring again to FIG. 6B, operation 626 may include operation 628depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on datastored on the device to which a provider of a communication network onwhich the device is configured to communicate has limited or no access.For example, FIG. 2, e.g., FIG. 2B, shows identifying one or moreservices configured to carry out at least one task for a device, theidentifying at least partly based on device data to which access isrestricted from a communication network provider module 228 identifyingone or more services (e.g., a service that shows where the nearestavailable taxi is to the device's location) identifying one or moreservices configured to be provided to a user of the device (e.g., asmartphone), said identifying at least partly based on data stored onthe device (e.g., location data) to which a provider of a communicationnetwork (e.g., a provider of a wireless router for the user to use atStarbucks, or an AT&T cellular provider) on which the device isconfigured to communicate has limited or no access (e.g., the positiondata is kept private by the device from outgoing traffic).

Referring again to FIG. 6B, operation 626 may include operation 630depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on datastored on the device to which the device manufacturer has limited or noaccess. For example, FIG. 2, e.g., FIG. 2B, shows identifying one ormore services configured to carry out at least one task for a device,the identifying at least partly based on device data to which access isrestricted from a device manufacturer module 230 identifying one or moreservices (e.g., a service that shows if there is a store within fivemiles of the user's location that has the item that the user isconsidering purchasing for a cheaper price), said identifying at leastpartly based on data stored on the device (e.g., a tablet device, e.g.,data stored on the device may be various spreadsheets created on acomputer and transferred to the device) to which the device manufacturer(e.g., ASUS) has limited or no access.

Referring now to FIG. 6C, operation 626 may include operation 632depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on datastored on the device to which a producer of one or more applicationsconfigured to be executed by the device has limited or no access. Forexample, FIG. 2, e.g., FIG. 2B, shows identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device data to which access is restricted froma device application producer module 232 identifying one or moreservices (e.g., a service that shows a route through Washington, D.C.,that avoids all roundabouts), said identifying at least partly based ondata stored on the device (e.g., an in-car driving assistant) to which aproducer of one or more applications (e.g., a music playing application)configured to be executed by the device has limited or no access (e.g.,the device may keep the music playing application from accessing itsstored routing information).

Referring again to FIG. 6C, operation 632 may include operation 634depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on datastored on the device to which a producer of an operating systemconfigured to be executed by the device has limited or no access. Forexample, FIG. 2, e.g., FIG. 2B, shows identifying one or more services,the identifying at least partly based on device data to which access isrestricted from a device operating system producer module 234identifying one or more services (e.g., a service that shows which barsin a particular neighborhood have the highest ratio of women to men)configured to be provided to a user of a device (e.g., a smartphonedevice), said identifying at least partly based on data stored on thedevice (e.g., data posted to social networking services indicatingwhether the user is single, married, or other) to which a producer of anoperating system (e.g., Google, the producer of the Android operatingsystem) configured to be executed by the device (e.g., the smartphone)has limited or no access.

Referring again to FIG. 6C, operation 502 may include operation 636depicting selecting a service, from one or more available services, saidselected service configured to be provided to a user of a device, saidselecting at least partly based on data regarding one or more propertiesof the device. For example, FIG. 2, e.g., FIG. 2C, shows identifying oneor more services configured to carry out at least one task for a device,the identifying at least partly based on device property data module 236selecting a service (e.g., a seat-picking on an airplane service), fromone or more available services, said selected service configured to beprovided to a user of a device (e.g., a computer device), said selectingat least partly based on one or more properties of the device (e.g., thedevice has a web browser opened that is pointed to an airline-ticketfinding web page).

Referring again to FIG. 6C, operation 636 may include operation 638depicting selecting a service, from one or more available servicescollected from one or more service providers, said selected serviceconfigured to be provided to a user of a device, said selecting at leastpartly based on data regarding one or more properties of the device. Forexample, FIG. 2, e.g., FIG. 2C, shows identifying one or more servicesfrom one or more service provider provided available services configuredto carry out at least one task for a device, the identifying at leastpartly based on device property data module 238 selecting a service(e.g., selecting a bicycling service), from one or more availableservices (e.g., a bicycling service, a fuel-consumption service, acar-tire-selecting service, and the like), collected from one or moreservice providers (e.g., an exercise service provider and a gasolinecompany provider), said selected service (e.g., a bicycling service)configured to be provided to a user of a device (e.g., a smartphone),said selecting at least partly based on data regarding one or moreproperties of the device (e.g., the device is designed to be strapped toa bicycle crossbar).

Referring again to FIG. 6C, operation 638 may include operation 640depicting selecting a service, from one or more available servicescollected from two or more discrete service providers, said selectedservice configured to be provided to a user of a device, said selectingat least partly based on data regarding one or more properties of thedevice. For example, FIG. 2, e.g., FIG. 2C, shows identifying one ormore services (e.g., a fluid drinking guidance service from two or moreavailable services provided by two or more discrete service providers,said one or more services (e.g., a fluid drinking guidance service forlong bicycle rides), and a traffic configured to carry out at least onetask for a device, the identifying at least partly based on deviceproperty data module 240 selecting a service, from one or more availableservices collected from two or more discrete service providers, saidselected service configured to be provided to a user of a device (e.g.,a smartphone device), said selecting at least partly based on dataregarding one or more properties of the device (e.g., data indicatingthat the device spends more than one hour a day traveling at speeds thatindicate that the device is being transported by bicycling).

Referring again to FIG. 6C, operation 640 may include operation 642depicting selecting a service, from one or more available servicescollected from a plurality of discrete service providers, said selectedservice configured to be provided to a user of a device, said selectingat least partly based on data regarding one or more properties of thedevice and at least partly based on one or more properties of one ormore of the plurality of discrete service providers. For example, FIG.2, e.g., FIG. 2C, shows identifying one or more services from two ormore available services provided by two or more discrete serviceproviders, said one or more services configured to carry out at leastone task for a device, the identifying at least partly based on deviceproperty data and partly based on one or more service providerproperties module 242 selecting a service (e.g., a coffee shopcomparison service) from one or more available services (e.g., fivedifferent coffee-shop comparison services, but one requires a barometerto determine which coffee shop is located in an area having the bestweather conditions to maintain bagel freshness) collected from aplurality of discrete service providers (e.g., Starbucks coffee companymight provide one, and Tully's coffee shops might provide one, Dunkin'Donuts may provide a service, and AT&T Communications), said selectedservice configured to be provided to a user of a device said selectingat least partly based on data regarding one or more properties of thedevice and at least partly based on one or more properties of one ormore of the plurality of discrete service providers (e.g., Starbucks,because they are the only provider that makes coffee beans, or AT&Tbecause they are the only telecommunications provider).

Referring now to FIG. 6D, operation 642 may include operation 644depicting selecting a service, from one or more available servicescollected from a plurality of discrete service providers, said selectedservice configured to be provided to a user of a device, said selectingat least partly based on data regarding one or more properties of thedevice and at least partly based on placement of one or more of theplurality of discrete service providers on a priority list. For example,FIG. 2, e.g., FIG. 2C, shows identifying one or more services from twoor more available services provided by two or more discrete serviceproviders, said one or more services configured to carry out at leastone task for a device, the identifying at least partly based on deviceproperty data and partly based on service provider priority listplacement module 244 selecting a service, from one or more availableservices collected from a plurality of discrete service providers, saidselected service configured to be provided to a user of a device, saidselecting at least partly based on data regarding one or more propertiesof the device and at least partly based on placement of one or more ofthe plurality of discrete service providers on a priority list (e.g.,service providers may pay, or prove themselves worthy, of a particularspot on a list, and thus be selected in that order; in some embodiments,a selection from the list may change the rank on the list (e.g., aservice provider that is selected may drop to the bottom or the nearbottom so that someone else is selected the next time).

Referring now to FIG. 6E, operation 642 may include operation 646depicting selecting a service, from one or more available servicescollected from a plurality of discrete service providers, said selectedservice configured to be provided to a user of a device, said selectingat least partly based on data regarding one or more properties of thedevice and at least partly based on a prior history between the deviceand one or more of the plurality of discrete service providers. Forexample, FIG. 2, e.g., FIG. 2C, shows identifying one or more servicesfrom two or more available services provided by two or more discreteservice providers, said one or more services configured to carry out atleast one task for a device, the identifying at least partly based ondevice property data and partly based on service provider history withdevice module 246 selecting a service, from one or more availableservices collected from a plurality of discrete service providers, saidselected service configured to be provided to a user of a device, saidselecting at least partly based on data regarding one or more propertiesof the device and at least partly based on a prior history between thedevice and one or more of the plurality of discrete service providers(e.g., one of the service providers may previously have provided aservice to the user, and the user may have ranked that service very low,so that service provider is less likely to be selected to provide adifferent service).

Referring again to FIG. 6E, operation 646 may include operation 648depicting selecting a service, from one or more available servicescollected from a plurality of discrete service providers, said selectedservice configured to be provided to a user of a device, said selectingat least partly based on data regarding one or more properties of thedevice and at least partly based on data indicating that the device haspreviously used one or more previous services provided by one or more ofthe plurality of discrete service providers. For example, FIG. 2, e.g.,FIG. 2C, shows identifying one or more services from two or moreavailable services provided by two or more discrete service providers,said one or more services configured to carry out at least one task fora device, the identifying at least partly based on device property dataand partly based on service provider previously providing service todevice module 248 selecting a service, from one or more availableservices collected from a plurality of discrete service providers, saidselected service configured to be provided to a user of a device, saidselecting at least partly based on data regarding one or more propertiesof the device and at least partly based on data indicating that thedevice has previously used one or more previous services provided by oneor more of the plurality of discrete service providers (e.g., Google mayprovide a map service and an email service, and if the device haspreviously used the map service, then that may add in priority forselection of Google to also provide the email service, particularly ifthe user has used the map service on different occasions, e.g.,indicating that the user is satisfied with the map service).

Referring now to FIG. 6F, operation 646 may include operation 650depicting selecting a service, from one or more available servicescollected from a plurality of discrete service providers, said selectedservice configured to be provided to a user of a device, said selectingat least partly based on data regarding one or more properties of thedevice and at least partly based on data indicating that one or moredevices having a characteristic in common with the device havepreviously used one or more previous services provided by one or more ofthe plurality of discrete service providers. For example, FIG. 2, e.g.,FIG. 2D, shows identifying one or more services from two or moreavailable services provided by two or more discrete service providers,said one or more services configured to carry out at least one task fora device, the identifying at least partly based on device property dataand partly based on the service provider providing the one or moreidentified services to a different device having a common characteristicwith the device module 250 selecting a service, from one or moreavailable services collected from a plurality of discrete serviceproviders, said selected service configured to be provided to a user ofa device, said selecting at least partly based on data regarding one ormore properties of the device and at least partly based on dataindicating that one or more devices having a characteristic in commonwith the device have previously used one or more previous servicesprovided by one or more of the plurality of discrete service providers(e.g., if the service to be provided is a mapping service, then deviceswith the same type of positioning sensor that have previously used theservice may increase that service's chances of being identified; or, inanother embodiment, if the service to be provided is a mapping serviceand the device is located in Seattle, then other mapping services thathave previously worked well for users located in Seattle may be morelikely to be identified).

Referring again to FIG. 6F, operation 642 may include operation 652depicting selecting a service, from one or more available servicescollected from a plurality of discrete service providers, said selectedservice configured to be provided to a user of a device, said selectingat least partly based on data regarding one or more properties of thedevice and at least partly based on a data sharing agreement with one ormore of the one or more discrete service providers. For example, FIG. 2,e.g., FIG. 2D, shows identifying one or more services from two or moreavailable services provided by two or more discrete service providers,said one or more services configured to carry out at least one task fora device, the identifying at least partly based on device property dataand partly based on service provider data sharing agreement module 252selecting a service, from one or more available services collected froma plurality of discrete service providers, said selected serviceconfigured to be provided to a user of a device, said selecting at leastpartly based on data regarding one or more properties of the device andat least partly based on a data sharing agreement with one or more ofthe one or more discrete service providers (e.g., if the identifyingentity has a data sharing agreement with a service provider that allowsthe identifying entity to have access to the data collected by theservice installed on the user's device, then this may make that serviceprovider's service more likely to be selected).

Referring now to FIG. 6G, operation 642 may include operation 654depicting selecting a service, from one or more available servicescollected from a plurality of discrete service providers, said selectedservice configured to be provided to a user of a device, said selectingat least partly based on data regarding one or more properties of thedevice and at least partly based on a prior relationship with one ormore of the one or more discrete service providers. For example, FIG. 2,e.g., FIG. 2E, shows identifying one or more services from two or moreavailable services provided by two or more discrete service providers,said one or more services configured to carry out at least one task fora device, the identifying at least partly based on device property dataand partly based on service provider prior contract module 254 selectinga service, from one or more available services collected from aplurality of discrete service providers, said selected serviceconfigured to be provided to a user of a device, said selecting at leastpartly based on data regarding one or more properties of the device andat least partly based on a prior relationship with one or more of theone or more discrete service providers (e.g., previously, the selectingentity may have successfully used the service provider's applicationsand/or services and been satisfied with them, which may lead toselection of that service provider's services).

Referring now to FIG. 6H, operation 502 may include operation 656depicting identifying one or more services configured to be provided toa user of a device, said identifying at least partly based on dataregarding one or more usage properties of the device. For example, FIG.2, e.g., FIG. 2F, shows identifying one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device usage information data module 256 identifying oneor more services (e.g., a soda pop vending machine inventory displayingservice) be provided to a user of a device (e.g., a user's smart phone),said identifying at least partly based on data regarding one or moreusage properties (e.g., the user uses a credit card transactionapplication installed on the device to buy a lot of sodas) of thedevice.

Referring again to FIG. 6H, operation 656 may include operation 658depicting identifying one or more services configured to be provided toa user of a device, said identifying at least partly based on dataincluding one or more locations at which the device is present. Forexample, FIG. 2, e.g., FIG. 2F, shows identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device position history information module 258identifying one or more services (e.g., identifying which grocery storehas the freshest inventory of blackberries) configured to be provided toa user of a device (e.g., a home shopping program running on a homecomputer), said identifying at least partly based on data including oneor more locations (e.g., a house) at which the device (e.g., the homecomputer) is present.

Referring again to FIG. 6H, operation 658 may include operation 660depicting identifying one or more calorie counting services configuredto be provided to a user of a device, said identifying at least partlybased on data including one or more restaurants at which the device ispresent. For example, FIG. 2, e.g., FIG. 2F, shows identifying a caloricintake service configured to carry out at least one task for a device,the identifying at least partly based on device position historyinformation module 660 identifying one or more calorie counting servicesconfigured to be provided to a user of a device (e.g., a watch that canload programs and take measurements designed to improve workoutefficiency), said identifying at least partly based on data includingone or more restaurants at which the device is present (e.g., which maybe based on location data, which may be the result of reading a GPSsensor, or triangulating position data).

Referring again to FIG. 6H, operation 656 may include operation 662depicting identifying one or more services configured to be provided toa user of a device, said identifying at least partly based on dataincluding one or more applications operating on the device. For example,FIG. 2, e.g., FIG. 2F, shows identifying one or more services configuredto carry out at least one task for a device, the identifying at leastpartly based on device application usage information data module 262identifying one or more services (e.g., activity planning, e.g.,scheduling a sports game based on people's calendars service) configuredto be provided to a user of the device, said identifying at least partlybased on data including one or more applications operating on the device(e.g., a calendar application).

Referring again to FIG. 6H, operation 656 may include operation 664depicting identifying one or more services configured to be provided toa user of a device, said identifying at least partly based on dataregarding one or more web pages downloaded on the device. For example,FIG. 2, e.g., FIG. 2F, shows identifying one or more services configuredto carry out at least one task for a device, the identifying at leastpartly based on device web browsing information data module 264identifying one or more services (e.g., a new restaurant findingservice) configured to be provided to a user of the device (e.g., auser's smartphone), said identifying at least partly based on dataregarding one or more web pages (e.g., web pages showing searches donefor new restaurants and visits to restaurant review web sites)downloaded (e.g., retrieved at the request of the user) on the device.

Referring again to FIG. 6H, operation 664 may include operation 666depicting identifying one or more personal finance management servicesconfigured to be provided to a user of a device, said identifying atleast partly based on data indicating that bank account websites aredownloaded three or more times a day, for at least two days. Forexample, FIG. 2, e.g., FIG. 2F, shows identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device web browsing information indicatingthree or more downloads a day from bank account websites data module 266identifying one or more personal finance management services configuredto be provided to a user of a device (e.g., a home personal computeruser), said identifying at least partly based on data indicating thatbank account websites are downloaded three or more times a day for atleast two days.

Referring again to FIG. 6H, operation 656 may include operation 668depicting identifying one or more services configured to be provided toa user of a device, said identifying at least partly based on dataincluding one or more types of applications operating on the device forlonger than a particular time. For example, FIG. 2, e.g., FIG. 2F, showsidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on particularapplication usage time amount data module 268 identifying one or moreservices (e.g., game services, e.g., offering services that will resultin purchasing a new weapon or other in-game item for a game) to beprovided to a user of a device (e.g., a game system, e.g., a Sony PlayStation Portable “PSP”), said identifying at least partly based on dataincluding one or more types of applications (e.g., games that are firstperson shooters or role-playing games) operating on the device forlonger than a particular time (e.g., after ten hours, a user may begetting bored, so this service allows him to earn a new weapon or otherin-game item).

Referring again to FIG. 6H, operation 668 may include operation 670depicting identifying one or more game playing services configured to beprovided to a user of a device, said identifying at least partly basedon data indicating that game applications are operating on the devicefor greater than fifty percent of the time that the device is active.For example, FIG. 2, e.g., FIG. 2F, shows identifying one or more gameplaying services configured to carry out at least one task for a device,the identifying at least partly based on particular game usage timeamount greater than a particular amount module 270 identifying one ormore game playing services (e.g., a new game finder) configured to beprovided to a user of a device (e.g., a user of a smartphone that can doother things besides play games), said identifying at least partly basedon data indicating that game applications are operating on the devicefor greater than fifty percent of the time that the device is active).

Referring now to FIG. 6I, operation 502 may include operation 672depicting identifying one or more data management services configured tobe provided to a user of a device, said identifying at least partlybased on data indicating that the device transmits more than aparticular amount of data per day. For example, FIG. 2, e.g., FIG. 2G,shows identifying one or more services configured to carry out at leastone task for a device, the identifying at least partly based on devicedata transmission amount module 272 identifying one or more datamanagement services (e.g., picture organizing services) configured to beprovided to a user of a device (e.g., a smartphone with a camera, orother digital camera), said identifying at least partly based on dataindicating that the device transmits more than a particular amount ofdata (e.g., more than 500 MB) of data per day).

Referring again to FIG. 6I, operation 502 may include operation 674depicting identifying one or more services configured to be provided toa user of a device, said identifying at least partly based on aninventory of protected data stored on the device. For example, FIG. 2,e.g., FIG. 2G, shows identifying one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on restricted device data inventory module 274 identifyingone or more services (e.g., a bandwidth regulator that changes whennon-priority information is uploaded or downloaded based on availablebandwidth) configured to be provided to a user of a device (e.g., anultraportable laptop computer, e.g., a netbook), said identifying atleast partly based on an inventory of protected data (e.g., an inventoryof what types of data are prevented from access by unauthorizedentities) stored on the device (e.g., stored in the device memory, orstored in a remote location to which the device can read and write).

Referring again to FIG. 6I, operation 674 may include operation 676depicting identifying one or more location-based delivery servicesconfigured to be provided to a user of a device, said identifying atleast partly based on an inventory showing that location data isprotected on the device. For example, FIG. 2, e.g., FIG. 2G, showsidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on restricteddevice data inventory indicating restricted position data module 276identifying one or more location-based delivery services configured tobe provided to a user of a device (e.g., a smartphone), said identifyingat least partly based on an inventory showing that location data isprotected (e.g., unauthorized users must receive authorization prior toaccessing) on the device.

Referring again to FIG. 6I, operation 674 may include operation 678depicting identifying one or more services configured to be provided toa user of a device, said identifying at least partly based on aninventory showing a number of previous locations stored and a number ofcontacts stored. For example, FIG. 2, e.g., FIG. 2G, shows identifyingone or more services configured to carry out at least one task for adevice, the identifying at least partly based on restricted device datainventory indicating a number of stored previous locations and a numberof stored previous contacts module 278 identifying one or more services(e.g., a service to show when the device user's friends are arriving atvarious locations) configured to be provided to a user of a device(e.g., a smartphone, e.g., an HTC Evo phone), said identifying at leastpartly based on an inventory showing a number of previous locationsstored and a number of contacts stored (e.g., in the contact list of thedevice).

Referring again to FIG. 6I, operation 502 may include operation 680depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on aninventory of one or more protected sensors on the device. For example,FIG. 2, e.g., FIG. 2G, shows identifying one or more services configuredto carry out at least one task for a device, the identifying at leastpartly based on restricted device sensor module 280 identifying one ormore services (e.g., displaying a rule book for a sport or game beingplayed in the proximity of the device) configured to be provided to auser of the device (e.g., a user of a tablet device, e.g., a MicrosoftSurface).

Referring again to FIG. 6I, operation 680 may include operation 682depicting identifying one or more network analyzing services configuredto be provided to a user of the device, said identifying at least partlybased on an inventory of one or more protected sensors, including aWi-Fi antenna, on the device. For example, FIG. 2, e.g., FIG. 2G, showsidentifying one or more data traffic analysis services configured tocarry out at least one task for a device the identifying at least partlybased on a restricted data radio module 282 identifying one or morenetwork analyzing services configured to be provided to a user of adevice (e.g., a portable hotspot), said identifying at least partlybased on an inventory of one or more protected sensors, including aWi-Fi antenna, on the device.

Referring again to FIG. 6I, operation 680 may include operation 684depicting identifying one or more services configured to be provided toa user of the device, said identifying at least partly based on aninventory of one or more protected sensors, including a barometricpressure sensor, on the device. For example, FIG. 2, e.g., FIG. 2G,shows identifying one or more weather analysis services configured tocarry out at least one task for a device, the identifying at leastpartly based on a restricted barometric pressure sensor module 284identifying one or more services (e.g., an ideal garden planting timecalculating service) configured to be provided to a user of a device(e.g., a home weather/garden device mounted in a user's house), saididentifying at least partly based on an inventory of one or moreprotected sensors, including a barometric pressure sensor, on thedevice.

Referring now to FIG. 8J, operation 502 may include operation 686depicting identifying a service configured to identify when one or moreentities listed in the device's contact list are within a particularproximity to the user of the device, said identifying at least partlybased on data regarding one or more properties of the device. Forexample, FIG. 2, e.g., FIG. 2G, shows identifying one or more alertservices configured to alert when one or more devices controlled by aperson in the device contact list is within a particular proximity tothe device, the identifying at least partly based on device data module244 identifying a service configured to identify when one or moreentities (e.g., people, house phones, businesses) listed in the device'scontact list are within a particular proximity (e.g., either throughtheir movement, if possible, or through the user's movement, or both) tothe user of the device (e.g., the user's smartphone), said identifyingat least partly based on data regarding one or more properties of thedevice (e.g., identifying that the device has stored more thantwenty-five contacts for whom it can be determined through checking thecontacts' publically-available Facebook status, are listed as “single”).

FIGS. 7A-7E depict various implementations of operation 504, depictingrequesting access to data collected by one or more portions of thedevice, in exchange for providing at least a portion of one of the oneor more identified services, according to embodiments. Referring now toFIG. 7A, operation 504 may include operation 702 depicting requestingaccess to data collected by one or more sensors of the device, inexchange for providing at least one of the one or more identifiedservices. For example, FIG. 3, e.g., FIG. 3A, shows access to dataacquired by one or more device sensors as negotiated result offacilitating a providing of one or more identified services requestingmodule 302 requesting access to data collected by one or more sensors ofthe device (e.g., a barometric pressure sensor), in exchange forproviding at least one of the one or more identified services (e.g., aservice that estimates how much time until it starts raining).

Referring again to FIG. 7A, operation 702 may include operation 704depicting requesting access to data collected by one or more globalpositioning sensors of the device, in exchange for providing at leastone of the one or more identified services. For example, FIG. 3, e.g.,FIG. 3A, shows access to data acquired by one or more device positioningsensors as negotiated result of facilitating a providing of one or moreidentified services requesting module 304 requesting access to datacollected by one or more global positioning sensors of the device, inexchange for providing at least one of the one or more identifiedservices (e.g., a service showing the user a list of the nearestautomated teller machine devices (“ATMs”) and what the service fee foreach of the ATMs is).

Referring again to FIG. 7A, operation 704 may include operation 706depicting requesting access to data collected by one or more globalpositioning sensors of the device, in exchange for providing one of thedetermined services that is a location-based service requiring access tothe one or more global positioning sensors of the device to becompleted. For example, FIG. 3, e.g., FIG. 3A shows access to dataacquired by one or more device positioning sensors as negotiated resultof facilitating a providing of an identified position-based servicerequiring access to the data acquired by the one or more devicepositioning sensors requesting module 306 requesting access to datacollected by one or more global positioning sensors of the device (e.g.,a user's smartphone), in exchange for providing one of the determinedservices that is a location based service (e.g., giving the user of thedevice directions to the nearest public bathroom and informationregarding its rating by other users) requiring access to the one or moreglobal positioning sensors of the device to be completed.

Referring again to FIG. 7A, operation 706 may include operation 708depicting requesting access to position data collected by one or moreglobal positioning sensors of the device, said data stored in devicememory, in exchange for providing one of the determined services that isa location-based service requiring access to the one or more globalpositioning sensors of the device to be completed. For example, FIG. 3,e.g., FIG. 3A shows access to position data acquired by one or moredevice positioning sensors and stored on the device as negotiated resultof facilitating a providing of an identified position-based servicerequiring access to the data acquired by the one or more devicepositioning sensors requesting module 308 requesting access to positiondata collected by one or more global positioning sensors of the device(e.g., a tablet device, e.g., a Google Nexus 7), said data stored indevice memory, in exchange for providing one of the determined services(e.g., mapping the population density in the vicinity of the user of thedevice) requiring access to the one or more global positioning sensorsof the device to be completed (e.g., even though the application couldmake a guess about the location, without access to the GPS sensor, thenthe service cannot be completed because the location of the devicecannot be accurately determined).

Referring again to FIG. 7A, operation 708 may include operation 710depicting requesting access to position data collected by one or moreglobal positioning sensors of the device, said data stored in devicememory, in exchange for providing a friend proximity alert service thatis location based and requires access to the one or more globalpositioning sensors of the device to be completed. For example, FIG. 3,e.g., FIG. 3A, shows access to position data acquired by one or moredevice positioning sensors and stored on the device as negotiated resultof facilitating a providing of an identified entity proximity alarmbased service requiring access to the data acquired by the one or moredevice positioning sensors requesting module 310 requesting access toposition data collected by one or more global positioning sensors of thedevice (e.g., a smartphone, e.g., an HTC Evo), said data stored indevice memory, in exchange for providing a friend proximity alertservice that is location based and requires access to the one or moreglobal positioning sensors of the device (e.g., without thisinformation, the service cannot be carried out) to be completed.

Referring again to FIG. 7A, operation 708 may include operation 712depicting requesting access to position data collected by one or morepositioning sensors of the device, said data stored in device memory, inexchange for transmitting, to the device, a friend proximity alertservice that is location based and requires access to the one or moreglobal positioning sensors of the device to be completed. For example,FIG. 3, e.g., FIG. 3A, shows access to position data acquired by one ormore device positioning sensors and stored on the device as negotiatedresult of transmitting, to the device, an identified entity proximityalarm based service requiring access to the data acquired by the one ormore device positioning sensors requesting module 312 requesting accessto position data collected by one or more positioning sensors of thedevice (e.g., a smartphone, e.g., an Apple iPhone), said data stored indevice memory, in exchange for transmitting, to the device, a friendproximity alert service (e.g., an application that is configured totransmit and receive the data needed to carry out the service, and todeliver the results and/or process the received data into results) thatis location based and requires access to the one or more globalpositioning sensors of the device to be completed (e.g., without theposition information, it cannot accurately determine which “friends” ofthe device are within proximity).

Referring now to FIG. 7B, operation 504 may include operation 714depicting requesting access, from the device, to data collected by oneor more portions of the device, in exchange for providing at least oneof the one or more identified services. For example, FIG. 3, e.g., FIG.3B, shows access to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingfrom the device module 314 requesting access (e.g., the ability to read,write, modify, transmit, alter, process, or otherwise obtain), from thedevice (e.g., a smartphone, e.g., a Nokia Lumia Windows Phone), to datacollected by one or more portions of the device (e.g., a contact list,or a list of applications that have been downloaded, or a memorandumdrafted by the user and stored on the device) in exchange for providingat least one of the one or more identified services (e.g., a “red zone”alert that alerts the user when her favorite football team is about toscore a touchdown).

Referring again to FIG. 7B, operation 714 may include operation 716depicting requesting access, from an application of the device thatcontrols access to one or more portions of the device, to data collectedby the one or more portions of the device, in exchange for providing atleast one of the one or more identified services. For example, FIG. 3,e.g., FIG. 3B, shows access to data acquired by the device as negotiatedresult of facilitating a providing of one or more identified servicesrequesting from an access control application of the device module 316requesting access, from an application of the device that controlsaccess to one or more portions of the device (e.g., a device operatingsystem, e.g., Windows 8 running on a Windows Surface tablet), to datacollected by the one or more portions of the device (e.g., twittermessages typed in through the keyboard and/or transmitted via thewireless radio), in exchange for providing at least one of the one ormore identified services (e.g., “enhanced twitter” which correctstwitter messages typed by the user and adds hash tags and keywords whichwill increase visibility).

Referring again to FIG. 7B, operation 714 may include operation 718depicting requesting access, from the device, which has beenpre-authorized by a user of the device to allow access under one or moreparticular conditions, to data collected by one or more portions of thedevice, in exchange for providing at least one of the one or moreidentified services. For example, FIG. 3, e.g., FIG. 3B, shows access todata acquired by the device as negotiated result of facilitating aproviding of one or more identified services requesting from the devicethat has user preauthorization to grant or deny access module 318requesting access, from the device (e.g., a smartphone, e.g., aBlackberry 8800), which has been pre-authorized by a user of the device(e.g., the user has said “allow all Google-based applications”) to allowaccess under one or more particular conditions (e.g., the service isauthored or approved by Google), to data collected by one or moreportions of the device (e.g., position data gathered from thepositioning sensor), in exchange for providing at least one of the oneor more identified services (e.g., context-based search engineservices).

Referring again to FIG. 7B, operation 718 may include operation 720depicting requesting access from the device, which has beenpre-authorized by the user of the device to allow access to one or moreapplications authored by a particular entity, to data collected by oneor more portions of the device, in exchange for providing at least oneof the one or more identified services. For example, FIG. 3, e.g., FIG.3B, shows access to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingfrom the device that has user preauthorization to grant or deny accessaccording to a service application author identity module 320 requestingaccess from the device (e.g., a Microsoft Surface tablet device), whichhas been pre-authorized by the user of the device to allow access to oneor more applications (e.g., Microsoft Word and Microsoft Excel, aword-processing program and a spreadsheet processing program,respectively) authored by a particular entity (e.g., Microsoft), to datacollected by one or more portions of the device (e.g., bank statementsdownloaded from the user's bank onto the device), in exchange forproviding at least one of the one or more identified services (e.g.,using Excel to deliver balanced personal budget services).

Referring again to FIG. 7B, operation 718 may include operation 722depicting requesting access from the device, which has beenpre-authorized by the user of the device to allow access to one or moreapplications authored by a same entity as one or more applicationspreviously operated by the device, to data collected by one or moreportions of the device, in exchange for providing at least one of theone or more identified services. For example. FIG. 3, e.g., FIG. 3B,shows access to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingfrom the device that has user preauthorization to grant access to one ormore applications having a common author entity as one or moreapplications previously operated by the device module 322 requestingaccess from the device, which has been pre-authorized by the user of thedevice (e.g., a portable gaming system) to allow access to one or moreapplications (e.g., a new game) authored by a same entity (e.g., a gameapplication authoring company, e.g., Zynga) as one or more applicationspreviously operated by the device (e.g., the device previously operatedone or more applications by Zynga), in exchange for providing at leastone of the one or more identified services (e.g., showing the device'sfriends from the contact list and their high scores of the game, whileplaying the game).

Referring again to FIG. 7B, operation 718 may include operation 724depicting requesting access from the device, which has beenpre-authorized by the user of the device to allow access to one or moreapplications that use a particular type of data, to data of theparticular type collected by one or more portions of the device, inexchange for providing at least one of the one or more services. Forexample, FIG. 3, e.g., FIG. 3B, shows requesting access from the device(e.g., a networked computer on an enterprise corporate environment),which has been pre-authorized by the user of the device (e.g., thenetworked computer) to allow access to one or more applications that usea particular type of data (e.g., an application that can take data froma work environment and run simulations and projections on the data), todata of the particular type (e.g., data from a particular project thatthe user is working on, e.g., Project A), collected by one or moreportions of the device (e.g., received, from the network, over a cable),in exchange for providing at least one of the one or more services(e.g., running a simulation with the data compared to real-worldevents).

Referring now to FIG. 7C, operation 504 may include operation 726depicting requesting access, from a user of the device, to datacollected by one or more portions of the device, in exchange forproviding at least one of the one or more identified services. Forexample, FIG. 3, e.g., FIG. 3C, shows access to data acquired by thedevice as negotiated result of facilitating a providing of one or moreidentified services requesting from device operator module 326requesting access, from a user of the device (e.g., a cellulartelephone), to data collected by one or more portions of the device(e.g., temperature data collected by a device thermometer that plugsinto an expansion port of the device), in exchange for providing atleast one of the one or more identified services (e.g., a weatherpredicting service).

Referring again to FIG. 3C, operation 726 may include operation 728depicting requesting access, from a user of the device, via the device,to data collected by one or more portions of the device, in exchange forproviding at least one of the one or more identified services. Forexample, FIG. 3, e.g., FIG. 3C, shows access to data acquired by thedevice as negotiated result of facilitating a providing of one or moreidentified services requesting, via the device, from device operatormodule 328 requesting access, from a user of the device (e.g., asmartphone, e.g., a Palm Pre), via the device (e.g., using the device tocommunicate the request for access, either through the screen or throughsome other device output mechanism), to data collected by one or moreportions of the device (e.g., a number of pictures in the picture album,but not the actual pictures themselves), in exchange for providing atleast one of the one or more identified services (e.g., providingrecommendations for hosting the user's picture album).

Referring again to FIG. 3C, operation 728 may include operation 730depicting requesting access, from a user of the device, by instructingthe device to carry out one or more operations to facilitate userinteraction, to data collected by one or more portions of the device, inexchange for providing at least one of the one or more identifiedservices. For example, FIG. 3, e.g., FIG. 3C, shows access to dataacquired by the device as negotiated result of providing of one or moreidentified services requesting, by instructing device to carry out userinteraction operations, from device operator module 330 requestingaccess, from a user of the device, by instructing the device to carryout one or more operations to facilitate user interaction (e.g.,requesting that the device display a screen that says “would you grantaccess to your contact list in exchange for receiving information aboutpotential new contacts in your home city”), to data collected by one ormore portions of the device (e.g., the contact list of a smartphone), inexchange for providing at least one of the one or more identifiedservices (e.g., using the contact list and known network information tosee if any “friends of friends” are located in the device's currentcity).

Referring again to FIG. 3C, operation 504 may include operation 732depicting facilitating, on the device, one or more operations thatfacilitate user interaction regarding access to data collected by one ormore portions of the device, in exchange for providing at least one ofthe one or more identified services. For example, FIG. 3, e.g., FIG. 3C,shows facilitation of user interaction regarding access to data acquiredby the device as negotiated result of facilitating a providing of one ormore identified services requesting module 332 facilitating, on thedevice, one or more operations that facilitate user interaction (e.g.,receiving speech from the user that authorizes release of one or morepictures stored on the device) regarding access to data collected by oneor more portions of the device (e.g., pictures captured by an imagecapturing sensor of the device, e.g., a smartphone), in exchange forproviding at least one of the one or more identified services (e.g.,providing a “celebrity look-a-like” service for pictures as a partygame).

Referring again to FIG. 7C, operation 732 may include operation 734depicting transmitting instructions to the device to carry out one ormore operations that facilitate user interaction regarding access todata collected by one or more portions of the device, in exchange forproviding at least one of the one or more identified services. Forexample, FIG. 3, e.g., FIG. 3C, shows transmission of instructions toproceed with a user interaction regarding access to data acquired by thedevice as negotiated result of facilitating a providing of one or moreidentified services requesting module 334 transmitting instructions tothe device to carry out one or more operations (e.g., displaying one ormore screens, accepting speech or touchscreen interaction, and the like)that facilitate user interaction regarding access to data (e.g.,position data collected by a device, e.g., a smartphone, positioningsensor) collected by one or more portions of the device (e.g., the GPSsensor of a Samsung smartphone), in exchange for providing at least oneof the one or more identified services (e.g., showing which restaurantsin the vicinity of the user's device are open past midnight).

Referring again to FIG. 7C, operation 732 may include operation 736depicting transmitting, to the device, an application that is configuredto carry out one or more operations that facilitate user interactionregarding access to data collected by one or more portions of thedevice, in exchange for providing at least one of the one or moreidentified services. For example, FIG. 3, e.g., FIG. 3C, showstransmission of an application that executes a user interactionregarding access to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingmodule 336 transmitting, to the device (e.g., a smartphone, e.g., aGoogle phone), an application that is configured to carry out one ormore operations (e.g., displaying a dialog box on the screen andaccepting touch screen input) regarding access to data collected by oneor more portions of the device (e.g., ambient light collected from alight sensor), in exchange for providing at least one of the one or moreidentified services (e.g., a service that lights up a smartphonenotification light when conditions are right to take a picture).

Referring again to FIG. 7C, operation 732 may include operation 738depicting facilitating, on the device, one or more operations thatfacilitate presentation of a request for access to the data collected byone or more portions of the device, in exchange for providing at leastone of the one or more identified services. For example, FIG. 3, e.g.,FIG. 3C, shows facilitation of presentation of request for access todata acquired by the device as negotiated result of facilitating aproviding of one or more identified services requesting module 338facilitating, on the device, one or more operations that facilitatepresentation of a request for access to the data collected by one ormore portions of the device (e.g., scheduled appointments entered usingvoice entry into a calendar of a smartphone), in exchange for providingat least one of the one or more identified services (e.g., a healthmanagement service that automatically schedules various appointments,e.g., eye appointments, physicals, dental appointments, haircuts,prescription refills, and the like).

Referring again to FIG. 7C, operation 732 may include operation 740depicting facilitating, on the device, one or more operations configuredto display a request for access to the data collected by one or moreportions of the device, in exchange for providing at least one of theone or more identified services. For example, FIG. 3, e.g., FIG. 3C,shows facilitation of display of request for access to data acquired bythe device as negotiated result of facilitating a providing of one ormore identified services requesting module 340 facilitating, on thedevice, one or more operations configured to display a request foraccess to the data collected by one or more portions of the device(e.g., how many playlists were created on the smartphone, and thefrequency to which those playlists are created, but not which songs arein those playlists), in exchange for providing at least one of the oneor more identified services (e.g., a playlist mixing service).

Referring now to FIG. 7D, operation 740 may include operation 742depicting facilitating, on the device, one or more operations configuredto display a request for access to the data collected by one or moreportions of the device, as a form of payment for providing at least oneof the one or more identified services. For example, FIG. 3, e.g., FIG.3C, shows facilitation of display of request for access to data acquiredby the device as a payment for facilitation of providing of one or moreidentified services requesting module 342 facilitating, on the device,one or more operations (e.g., causing the speaker of the device, e.g.,the portable navigation system, to read instructions) to display arequest (e.g., the reading of instructions coupled with displaying alarge “yes” box on the screen) for access to the data collected by oneor more portions of the device (e.g., speed data collected by thespeedometer), as a form of payment for providing at least one of the oneor more identified services (e.g., tracking gas mileage and suggestingoptimum speed services).

Referring again to FIG. 7D, operation 740 may include operation 744depicting facilitating, on the device, one or more operations configuredto display an example of the one or more identified services, and topresent a request for access to the data collected by one or moreportions of the device as a prerequisite for providing at least one ofthe one or more identified services. For example, FIG. 3, e.g., FIG. 3C,shows facilitation of display of request for access to data acquired bythe device as a necessary condition precedent to facilitation ofproviding of one or more identified services requesting module 344facilitating, on the device, one or more operations configured todisplay an example of the one or more identified services (e.g., asample map of ice cream shops in a famous vicinity, e.g., Times Square,to show an example of the ice cream shop finder), and to present arequest for access to the data (e.g., position data) collected by one ormore portions of the device (e.g., the GPS sensor of an Apple iPhone) asa prerequisite for providing at least one of the one or more identifiedservices (e.g., “We can't show you the ice cream shops in your area tillwe have access to this data”).

Referring now to FIG. 7E, operation 504 may include operation 746depicting facilitating, on the device, presentation of an example ofproviding the one or more identified services. For example, FIG. 3,e.g., FIG. 3D, shows presentation of an example of providing the one ormore services facilitating module 346 facilitating (e.g., taking one ormore steps to assist in the carrying out of), on the device (e.g., asmartphone, e.g., a Windows-branded phone), presentation of an exampleof providing the one or more services (e.g., showing a sample newplaylist that could be created with access to the names of songs storedin the user's music cloud).

Referring again to FIG. 7E, operation 504 may include operation 748depicting facilitating, on the device, presentation of a request foraccess to data collected by one or more portions of the device as amanner of carrying out the one or more identified services similarly tothe presented example. For example, FIG. 3, e.g., FIG. 3D, showspresentation of a request for access to the data acquired by the deviceas a manner of carrying out the one or more services as shown in thepresentation of the example facilitating module 348 facilitating, on thedevice (e.g., the Windows-branded phone), presentation of a request foraccess to data (e.g., for access to a list of songs) collected by one ormore portions of the device (e.g., downloaded from a place and receivedat the phone, or stored in the cloud after being purchased using anaccount associated with the phone) as a manner of carrying out the oneor more identified services (e.g., the access to the list of songs ispresented as a manner of carrying out the auto-playlisting service)similarly to the presented example (e.g., the showing of a sample newplaylist).

Referring again to FIG. 7E, operation 748 may include operation 750depicting facilitating, on the device, presentation of the request foraccess to data collected by one or more portions of the device as anecessary condition for carrying out the one or more identifiedservices. For example, FIG. 3, e.g., FIG. 3D shows presentation of arequest for access to the data acquired by the device as a necessarycondition of carrying out the one or more services as shown in thepresentation of the example facilitating module 350 facilitating, on thedevice, presentation of the request for access to data collected by oneor more portions of the device (e.g., data regarding the user's webbrowsing history) as a necessary condition for carrying out the one ormore identified services (e.g., suggesting new websites that the usermight be interested in browsing).

Referring again to FIG. 7E, operation 748 may include operation 752depicting facilitating, on the device, presentation of the request foraccess to data collected by one or more portions of the device as a termof service agreement for carrying out the one or more identifiedservices. For example, FIG. 3, e.g., FIG. 3D, shows presentation of arequest for access to the data acquired by the device as a form ofpayment for carrying out the one or more services as shown in thepresentation of the example facilitating module 352 facilitating, on thedevice, presentation of the request for access to data collected by oneor more portions of the device (e.g., listings of various wirelessnetworks detected by the wireless radio) as a term of service agreement(e.g., as part of the EULA when the user subscribes to the service) forcarrying out the one or more identified services (e.g., showing a map ofareas covered by public wireless networks).

FIGS. 8A-8E depict various implementations of operation 506 depictingproviding at least a portion of the one or more services after receivingaccess to the data collectable by one or more portions of the device,according to embodiments. Referring now to FIG. 8A, operation 506 mayinclude operation 802 depicting providing at least a portion of the oneor more services after receiving access to the data previously collectedby one or more portions of the device. For example, FIG. 4, e.g., FIG.4A, shows provision of at least a portion of the one or more servicesfacilitating upon receipt of negotiated access to data previouslyacquired by the device module 402 providing at least a portion of theone or more services (e.g., for the service “show all the ATMs close tothe user's device location,” providing a list of the ATMs to the deviceand letting the device do further filtering) after receiving access tothe data (e.g., position data) previously collected by one or moreportions of the device.

Referring again to FIG. 8A, operation 506 may include operation 804depicting providing at least a portion of the one or more services afterreceiving access to data as it is collected by one or more sensors ofthe device. For example, FIG. 4, e.g., FIG. 4A, shows provision of atleast a portion of the one or more services facilitating upon receipt ofnegotiated access to data as it is obtained by the device module 404providing at least a portion of the one or more services (e.g., making adownload of an application that carries out the service available) afterreceiving access to data (e.g., velocity data) as it is collected by oneor more sensors (e.g., velocity sensors) of the device (e.g., an in carmotor vehicle control system).

Referring again to FIG. 8A, operation 506 may include operation 806depicting providing at least a portion of the one or more services afterreceiving permission to access data to be collected by one or moresensors of the device at a later time. For example, FIG. 4, e.g., FIG.4A, shows provision of at least a portion of the one or more servicesfacilitating upon receipt of negotiated access to data after it isobtained by the device module 406 providing at least a portion of theone or more services providing at least a portion of the one or moreservices (e.g., providing one or more instructions for carrying out atleast a portion of a service that identifies lower-calorie restaurantalternatives near any restaurant the user chooses) after receivingpermission to access to data to be collected by one or more sensors(e.g., data of the review of the restaurant typed by the keyboard of thedevice, e.g., the sensor of the computer) at a later time (e.g., whenthe user gets back from the restaurant and fills out the review on hercomputer).

Referring again to FIG. 8A, operation 506 may include operation 808depicting providing at least a portion of the one or more services afterreceiving access to the data collectable by one or more portions of thedevice. For example, FIG. 4, e.g., FIG. 4A, shows provision of at leasta portion of the one or more services facilitating upon receipt ofnegotiated access to data obtained by a device environment interactioncomponent module 408 providing at least a portion of the one or moreservices (e.g., providing computing power and/or memory to carry out aservice of tracking weather and light phenomena for a garden planningservice) after receiving access to the data (e.g., barometer,temperature, and ambient light data) collectable by one or more portionsof the device (e.g., a smartphone with weather detecting extensions).

Referring again to FIG. 8A, operation 506 may include operation 810depicting providing a location at which one or more applications thatare configured to perform the services can be downloaded, afterreceiving access to the data collectable by one or more portions of thedevice. For example, FIG. 4, e.g., FIG. 4A, shows providing a locationat which one or more applications configured to perform one or moreservices are configured to be downloaded upon receipt of negotiatedaccess to data acquired by the device module 410 providing a location(e.g., a server, e.g., a network computer, e.g., providing a webaddress) at which one or more applications that are configured toperform the services can be downloaded (e.g., retrieved by the device),after receiving access to the data collectable by one or more portionsof the device (e.g., a tablet device, e.g., an Apple iPad).

Referring now to FIG. 8B, operation 506 may include operation 812depicting providing at least a portion of a physical activity trackerservice after receiving access to the data collectable by one or moreportions of the device. For example, FIG. 4, e.g., FIG. 4B, showsprovision of at least a portion of a physical activity tracker servicefacilitating upon receipt of negotiated access to data acquired by thedevice module 412 providing at least a portion of a physical activitytracker service after receiving access to the data (e.g., calorieburning data) collectable by one or more portions of the device (e.g.,the device, e.g., a treadmill at a gym) has a heart rate monitor, whichit then uses the data from that to extrapolate calorie burning)

Referring again to FIG. 8B, operation 812 may include operation 814depicting providing an application that carries out the physicalactivity tracker service, after receiving access to the data collectableby one or more portions of the device. For example, FIG. 4, e.g., FIG.4B, shows facilitating a download of an application configured to carryout at least a portion of a physical activity tracker servicefacilitating upon receipt of negotiated access to data acquired by thedevice module 414 providing an application (e.g., a program running on asmartphone) that carries out a physical activity tracker service, afterreceiving access to the data collectable by one or more portions of thedevice (e.g., a speedometer of the device, e.g., a smartphone device).

Referring again to FIG. 8B, operation 812 may include operation 816depicting providing access to a data repository configured to receivedata related to the physical activity tracker service from the device,after receiving access to the data collectable by one or more portionsof the device. For example, FIG. 4, e.g., FIG. 4B, shows providingaccess to a data repository configured to receive data related to thephysical activity tracker service upon receipt of negotiated access todata acquired by the device module 416 providing access to a datarepository (e.g., a remote location where data is stored on behalf ofone or more devices) configured to receive data (e.g., distancetraveled) related to the physical activity tracker service from thedevice (e.g., a piece of clothing wired to track and relay data), afterreceiving access to the data collectable by one or more portions of thedevice (e.g., a separate piece of equipment, e.g., a home server, thatis linked to the piece of clothing that tracks and relays data, grantsaccess to the data collectible by the piece of clothing with trackingequipment).

Referring again to FIG. 8B, operation 816 may include operation 818depicting providing access to a data repository configured to receivedata related to the physical activity tracker service from the device,after receiving access to device acceleration data collectable by anaccelerometer of the device. For example, FIG. 4, e.g., FIG. 4B, showsproviding access to a data repository configured to receive data relatedto the physical activity tracker service upon receipt of negotiatedaccess to acceleration data acquired by a device accelerometer module418 providing access to a data repository (e.g., a location that storesdata) configured to receive data (e.g., data regarding acceleration)related to the physical activity tracker service from the device (e.g.,a personal training watch worn by a user), after receiving access todevice acceleration data collectable by an accelerometer of the device.

Referring again to FIG. 8B, operation 816 may include operation 820depicting providing access to a data repository configured to receivedata related to the physical activity tracker service from the device,after receiving access to activity name information spoken into a devicemicrophone and stored on the device. For example, FIG. 4, e.g., FIG. 4B,shows providing access to a data repository configured to receive datarelated to the physical activity tracker service upon receipt ofnegotiated access to activity name inputted to the device by a user andstored in the device module 420 providing access to a data repository(e.g., one or more structures, e.g., servers, hard drives, removablemedia, physical media, ordered matter, or any structure designed tostore data) configured to receive data related to the physical activitytracker service (e.g., to receive name of activity, duration, andintensity level), after receiving access to activity name information(e.g., “Spin class, thirty minutes, intensity eight out of ten”) spokeninto a device microphone and stored on the device.

All of the above U.S. patents, U.S. patent application publications,U.S. patent applications, foreign patents, foreign patent applicationsand non-patent publications referred to in this specification and/orlisted in any Application Data Sheet, are incorporated herein byreference, to the extent not inconsistent herewith.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.).

It will be further understood by those within the art that if a specificnumber of an introduced claim recitation is intended, such an intentwill be explicitly recited in the claim, and in the absence of suchrecitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to claims containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations).

Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that typically a disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms unless context dictates otherwise. For example, the phrase “Aor B” will be typically understood to include the possibilities of “A”or “B” or “A and B.”

With respect to the appended claims, those skilled in the art willappreciate that recited operations therein may generally be performed inany order. Also, although various operational flows are presented in asequence(s), it should be understood that the various operations may beperformed in other orders than those which are illustrated, or may beperformed concurrently. Examples of such alternate orderings may includeoverlapping, interleaved, interrupted, reordered, incremental,preparatory, supplemental, simultaneous, reverse, or other variantorderings, unless context dictates otherwise. Furthermore, terms like“responsive to,” “related to,” or other past-tense adjectives aregenerally not intended to exclude such variants, unless context dictatesotherwise.

This application may make reference to one or more trademarks, e.g., aword, letter, symbol, or device adopted by one manufacturer or merchantand used to identify and/or distinguish his or her product from those ofothers. Trademark names used herein are set forth in such language thatmakes clear their identity, that distinguishes them from commondescriptive nouns, that have fixed and definite meanings, or, in many ifnot all cases, are accompanied by other specific identification usingterms not covered by trademark. In addition, trademark names used hereinhave meanings that are well-known and defined in the literature, or donot refer to products or compounds for which knowledge of one or moretrade secrets is required in order to divine their meaning Alltrademarks referenced in this application are the property of theirrespective owners, and the appearance of one or more trademarks in thisapplication does not diminish or otherwise adversely affect the validityof the one or more trademarks. All trademarks, registered orunregistered, that appear in this application are assumed to include aproper trademark symbol, e.g., the circle R or bracketed capitalization(e.g., [trademark name]), even when such trademark symbol does notexplicitly appear next to the trademark. To the extent a trademark isused in a descriptive manner to refer to a product or process, thattrademark should be interpreted to represent the corresponding productor process as of the date of the filing of this patent application.

Those skilled in the art will appreciate that the foregoing specificexemplary processes and/or devices and/or technologies arerepresentative of more general processes and/or devices and/ortechnologies taught elsewhere herein, such as in the claims filedherewith and/or elsewhere in the present application.

1-161. (canceled)
 162. A device, comprising: a one or more servicesconfigured to carry out at least one task for a device identifying atleast partly based on device data module; an access to data acquired bythe device as negotiated result of facilitating a providing of one ormore identified services requesting module; and a provision of at leasta portion of the one or more services facilitating upon receipt ofnegotiated access to data acquired by the device module.
 163. The deviceof claim 162, wherein said one or more services configured to carry outat least one task for a device identifying at least partly based ondevice data module comprises: an identifying a notification presentationservice configured to notify when one or more entities are within aparticular proximity to the device, the identifying at least partlybased on device data module.
 164. (canceled)
 165. The device of claim163, wherein said identifying a notification presentation serviceconfigured to notify when one or more entities are within a particularproximity to the device, the identifying at least partly based on devicedata module comprises: an identifying a notification presentationservice configured to notify when one or more entities are within aparticular proximity to the device, the identifying at least partlybased on data indicating that a device contact list has restrictedaccess module.
 166. (canceled)
 167. (canceled)
 168. (canceled) 169.(canceled)
 170. The device of claim 162, wherein said one or moreservices configured to carry out at least one task for a deviceidentifying at least partly based on device data module comprises: anidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on devicesensor data module.
 171. The device of claim 170, wherein saididentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on devicesensor data module comprises: an identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device image capturing sensor data module. 172.(canceled)
 173. The device of claim 170, wherein said identifying one ormore services configured to carry out at least one task for a device,the identifying at least partly based on device sensor data modulecomprises: an identifying one or more services configured to carry outat least one task for a device, the identifying at least partly based ondevice sensor data module.
 174. The device of claim 173, wherein saididentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on devicesensor data module comprises: an identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device sensor data to which access isrestricted to at least a portion of the device module.
 175. The deviceof claim 162, wherein said one or more services configured to carry outat least one task for a device identifying at least partly based ondevice data module comprises: an identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device data to which access is restricted fromone or more external entities module.
 176. (canceled)
 177. The device ofclaim 175, wherein said identifying one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device data to which access is restricted from one ormore external entities module comprises: an identifying one or moreservices configured to carry out at least one task for a device, theidentifying at least partly based on device data to which access isrestricted from a device manufacturer module.
 178. The device of claim175, wherein said identifying one or more services configured to carryout at least one task for a device, the identifying at least partlybased on device data to which access is restricted from one or moreexternal entities module comprises: an identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device data to which access is restricted froma device application producer module.
 179. The device of claim 178,wherein said identifying one or more services configured to carry out atleast one task for a device, the identifying at least partly based ondevice data to which access is restricted from a device applicationproducer module comprises: an identifying one or more services, theidentifying at least partly based on device data to which access isrestricted from a device operating system producer module.
 180. Thedevice of claim 162, wherein said one or more services configured tocarry out at least one task for a device identifying at least partlybased on device data module comprises: an identifying one or moreservices configured to carry out at least one task for a device, theidentifying at least partly based on device property data module. 181.The device of claim 180, wherein said identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device property data module comprises: anidentifying one or more services from one or more service providerprovided available services configured to carry out at least one taskfor a device, the identifying at least partly based on device propertydata module.
 182. The device of claim 181, wherein said identifying oneor more services from one or more service provider provided availableservices configured to carry out at least one task for a device, theidentifying at least partly based on device property data modulecomprises: an identifying one or more services from two or moreavailable services provided by two or more discrete service providers,said one or more services configured to carry out at least one task fora device, the identifying at least partly based on device property datamodule.
 183. The device of claim 182, wherein said identifying one ormore services from two or more available services provided by two ormore discrete service providers, said one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device property data module comprises: an identifyingone or more services from two or more available services provided by twoor more discrete service providers, said one or more services configuredto carry out at least one task for a device, the identifying at leastpartly based on device property data and partly based on one or moreservice provider properties module.
 184. The device of claim 183,wherein said identifying one or more services from two or more availableservices provided by two or more discrete service providers, said one ormore services configured to carry out at least one task for a device,the identifying at least partly based on device property data and partlybased on one or more service provider properties module comprises: anidentifying one or more services from two or more available servicesprovided by two or more discrete service providers, said one or moreservices configured to carry out at least one task for a device, theidentifying at least partly based on device property data and partlybased on service provider priority list placement module.
 185. Thedevice of claim 183, wherein said identifying one or more services fromtwo or more available services provided by two or more discrete serviceproviders, said one or more services configured to carry out at leastone task for a device, the identifying at least partly based on deviceproperty data and partly based on one or more service providerproperties module comprises: an identifying one or more services fromtwo or more available services provided by two or more discrete serviceproviders, said one or more services configured to carry out at leastone task for a device, the identifying at least partly based on deviceproperty data and partly based on service provider history with devicemodule.
 186. The device of claim 185, wherein said identifying one ormore services from two or more available services provided by two ormore discrete service providers, said one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device property data and partly based on serviceprovider history with device module comprises: an identifying one ormore services from two or more available services provided by two ormore discrete service providers, said one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device property data and partly based on serviceprovider previously providing service to device module.
 187. (canceled)188. (canceled)
 189. The device of claim 183, wherein said identifyingone or more services from two or more available services provided by twoor more discrete service providers, said one or more services configuredto carry out at least one task for a device, the identifying at leastpartly based on device property data and partly based on one or moreservice provider properties module comprises: an identifying one or moreservices from two or more available services provided by two or morediscrete service providers, said one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device property data and partly based on serviceprovider prior contract module.
 190. The device of claim 162, whereinsaid one or more services configured to carry out at least one task fora device identifying at least partly based on device data modulecomprises: an identifying one or more services configured to carry outat least one task for a device, the identifying at least partly based ondevice usage information data module.
 191. The device of claim 190,wherein said identifying one or more services configured to carry out atleast one task for a device, the identifying at least partly based ondevice usage information data module comprises: an identifying one ormore services configured to carry out at least one task for a device,the identifying at least partly based on device usage information datamodule.
 192. (canceled)
 193. The device of claim 190, wherein saididentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on device usageinformation data module comprises: an identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device application usage information datamodule.
 194. The device of claim 190, wherein said identifying one ormore services configured to carry out at least one task for a device,the identifying at least partly based on device usage information datamodule comprises: an identifying one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on device web browsing information data module.
 195. Thedevice of claim 194, wherein said identifying one or more servicesconfigured to carry out at least one task for a device, the identifyingat least partly based on device web browsing information data modulecomprises: an identifying one or more services configured to carry outat least one task for a device, the identifying at least partly based ondevice web browsing information indicating three or more downloads a dayfrom bank account websites data module.
 196. (canceled)
 197. (canceled)198. (canceled)
 199. The device of claim 162, wherein said one or moreservices configured to carry out at least one task for a deviceidentifying at least partly based on device data module comprises: anidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on restricteddevice data inventory module.
 200. (canceled)
 201. The device of claim199, wherein said identifying one or more services configured to carryout at least one task for a device, the identifying at least partlybased on restricted device data inventory module comprises: anidentifying one or more services configured to carry out at least onetask for a device, the identifying at least partly based on restricteddevice data inventory indicating a number of stored previous locationsand a number of stored previous contacts module.
 202. The device ofclaim 162, wherein said one or more services configured to carry out atleast one task for a device identifying at least partly based on devicedata module comprises: an identifying one or more services configured tocarry out at least one task for a device, the identifying at leastpartly based on restricted device sensor module.
 203. (canceled) 204.(canceled)
 205. (canceled)
 206. The device of claim 162, wherein saidaccess to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingmodule comprises: an access to data acquired by one or more devicesensors as negotiated result of facilitating a providing of one or moreidentified services requesting module.
 207. (canceled)
 208. (canceled)209. (canceled)
 210. (canceled)
 211. (canceled)
 212. The device of claim162, wherein said access to data acquired by the device as negotiatedresult of facilitating a providing of one or more identified servicesrequesting module comprises: an access to data acquired by the device asnegotiated result of facilitating a providing of one or more identifiedservices requesting from the device module.
 213. The device of claim212, wherein said access to data acquired by the device as negotiatedresult of facilitating a providing of one or more identified servicesrequesting from the device module comprises: an access to data acquiredby the device as negotiated result of facilitating a providing of one ormore identified services requesting from an access control applicationof the device module.
 214. The device of claim 212, wherein said accessto data acquired by the device as negotiated result of facilitating aproviding of one or more identified services requesting from the devicemodule comprises: an access to data acquired by the device as negotiatedresult of facilitating a providing of one or more identified servicesrequesting from the device that has user preauthorization to grant ordeny access according to one or more particular conditions module. 215.(canceled)
 216. (canceled)
 217. (canceled)
 218. (canceled) 219.(canceled)
 220. (canceled)
 221. The device of claim 162, wherein saidaccess to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingmodule comprises: a facilitation of user interaction regarding access todata acquired by the device as negotiated result of facilitating aproviding of one or more identified services requesting module.
 222. Thedevice of claim 221, wherein said facilitation of user interactionregarding access to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingmodule comprises: a transmission of instructions to proceed with a userinteraction regarding access to data acquired by the device asnegotiated result of facilitating a providing of one or more identifiedservices requesting module.
 223. The device of claim 221, wherein saidfacilitation of user interaction regarding access to data acquired bythe device as negotiated result of facilitating a providing of one ormore identified services requesting module comprises: a transmission ofan application that executes a user interaction regarding access to dataacquired by the device as negotiated result of facilitating a providingof one or more identified services requesting module.
 224. (canceled)225. The device of claim 223, wherein said facilitation of userinteraction regarding access to data acquired by the device asnegotiated result of facilitating a providing of one or more identifiedservices requesting module comprises: a facilitation of display ofrequest for access to data acquired by the device as negotiated resultof facilitating a providing of one or more identified servicesrequesting module.
 226. The device of claim 225, wherein saidfacilitation of display of request for access to data acquired by thedevice as negotiated result of facilitating a providing of one or moreidentified services requesting module comprises: a facilitation ofdisplay of request for access to data acquired by the device as apayment for facilitation of providing of one or more identified servicesrequesting module.
 227. (canceled)
 228. The device of claim 162, whereinsaid access to data acquired by the device as negotiated result offacilitating a providing of one or more identified services requestingmodule comprises: a presentation of an example of providing the one ormore services facilitating module; and a presentation of a request foraccess to the data acquired by the device as a manner of carrying outthe one or more services as shown in the presentation of the examplefacilitating module.
 229. The device of claim 228, wherein saidpresentation of a request for access to the data acquired by the deviceas a manner of carrying out the one or more services as shown in thepresentation of the example facilitating module comprises: apresentation of a request for access to the data acquired by the deviceas a necessary condition of carrying out the one or more services asshown in the presentation of the example facilitating module.
 230. Thedevice of claim 228, wherein said presentation of a request for accessto the data acquired by the device as a manner of carrying out the oneor more services as shown in the presentation of the examplefacilitating module comprises: a presentation of a request for access tothe data acquired by the device as a terms of service agreement forcarrying out the one or more services as shown in the presentation ofthe example facilitating module.
 231. The device of claim 162, whereinsaid provision of at least a portion of the one or more servicesfacilitating upon receipt of negotiated access to data acquired by thedevice module comprises: a provision of at least a portion of the one ormore services facilitating upon receipt of negotiated access to datapreviously acquired by the device module.
 232. (canceled) 233.(canceled)
 234. (canceled)
 235. (canceled)
 236. (canceled) 237.(canceled)
 238. (canceled)
 239. (canceled)
 240. (canceled)
 241. Adevice, comprising: one or more general purpose integrated circuitsconfigured to receive instructions to configure as a one or moreservices configured to carry out at least one task for a deviceidentifying at least partly based on device data module at one or morefirst particular times; one or more general purpose integrated circuitsconfigured to receive instructions to configure as a access to dataacquired by the device as negotiated result of facilitating a providingof one or more identified services requesting module at one or moresecond particular times; and one or more general purpose integratedcircuits configured to receive instructions to configure as a provisionof at least a portion of the one or more services facilitating uponreceipt of negotiated access to data acquired by the device module atone or more third particular times.
 242. (canceled)
 243. (canceled) 244.A device, comprising: one or more elements of programmable hardwareprogrammed to function as a one or more services configured to carry outat least one task for a device identifying at least partly based ondevice data module; one or more elements of programmable hardwareprogrammed to function as a access to data acquired by the device asnegotiated result of facilitating a providing of one or more identifiedservices requesting module; and one or more elements of programmablehardware programmed to function as a provision of at least a portion ofthe one or more services facilitating upon receipt of negotiated accessto data acquired by the device module.